npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agent-relay/personas

v6.0.13

Published

Relay-maintained AgentWorkforce personas for use with `agentworkforce install`.

Readme

@agent-relay/personas

Relay-maintained AgentWorkforce personas.

This package is the canonical home for Relay-specific personas. Generic, internal personas (especially persona-maker, which agentworkforce create depends on) remain built into AgentWorkforce. Relay-oriented personas live here so their prompts, docs, tests, release cadence, and domain assumptions stay close to the Relay source they describe.

Install

Install all personas from this pack:

agentworkforce install @agent-relay/personas

Install a single persona by id:

agentworkforce install @agent-relay/personas --persona relay-orchestrator

Pin a specific version:

agentworkforce install @agent-relay/[email protected]

You can also install directly from a local checkout of this repo:

agentworkforce install ./packages/personas
agentworkforce install ./packages/personas --persona relay-orchestrator

Personas

| Persona | Purpose | | --- | --- | | relay-orchestrator | Coordinates Relay implementation and operations work via a headless orchestrator that spawns larger models as needed. | | agent-relay-workflow | Authors complete, runnable agent-relay workflow artifacts that follow the workflow skill contract and ship via GitHub primitives. | | agent-relay-e2e-conductor | Drives full sage ↔ cloud ↔ Slack end-to-end validation across a real docker-compose stack. | | cloud-sandbox-infra | Implements cloud sandbox provisioning, session management, credentials, executor wiring, and Daytona SDK integration. | | cloud-slack-proxy-guard | Owns the canonical POST /api/v1/proxy/slack route — allow-listed methods, shared-secret auth, rate limits, audit log, stable response envelope. | | sage-slack-egress-migrator | Migrates sage Slack egress off direct NangoClient and onto the @relayfile/sdk ConnectionProvider abstraction with no hardcoded providerConfigKey defaults. | | sage-proactive-rewirer | Rewires sage's proactive Slack paths to resolve connectionId and providerConfigKey from stored state instead of guessing. | | opencode-workflow-specialist | Diagnoses and repairs opencode-based agent-relay workflow failures across SDK, broker, cloud bootstrap, and CLI layers. |

Persona pack metadata

Personas are surfaced to AgentWorkforce via the standard pack contract:

{
  "name": "@agent-relay/personas",
  "agentworkforce": {
    "personas": "personas"
  }
}

agentworkforce install discovers persona JSON files inside the directory named by agentworkforce.personas. Each file in personas/ is a single persona, with its file basename matching the persona id.

Persona shape

Each persona JSON file has the following shape, matching the AgentWorkforce persona schema:

{
  "id": "string (matches filename basename)",
  "intent": "string",
  "tags": ["..."],
  "description": "string",
  "skills": [
    { "id": "string", "source": "url-or-pkg", "description": "string" }
  ],
  "tiers": {
    "best":        { "harness": "...", "model": "...", "systemPrompt": "...", "harnessSettings": { } },
    "best-value":  { "harness": "...", "model": "...", "systemPrompt": "...", "harnessSettings": { } },
    "minimum":     { "harness": "...", "model": "...", "systemPrompt": "...", "harnessSettings": { } }
  }
}

skills is optional. tiers is required and must contain at least one of best, best-value, or minimum. Persona prompts are model-agnostic where possible.

Validation

Run the persona validator from the package directory:

npm --prefix packages/personas run validate

The validator checks every JSON file under personas/:

  • file is valid JSON
  • id is present and matches the file basename
  • intent, description, and tiers are present
  • at least one of the three known tiers (best, best-value, minimum) is set
  • each tier has harness, model, and systemPrompt

Versioning and publishing

This package versions in lockstep with the Relay monorepo and is published alongside the rest of the @agent-relay/* packages by the root publish workflow. Version bumps happen at the monorepo level — do not bump packages/personas/package.json independently.

Migration notes

Persona content was migrated from AgentWorkforce/workforce/personas with stable persona ids and file basenames preserved. Relay-specific operational guidance lives next to the Relay source it depends on; for context on the migration see AgentWorkforce/workforce#38 and AgentWorkforce/workforce#42.