TokenRing Community Registry

A registry of community-contributed agents, tools, and workflows for TokenRing One. Browse and install them from the Marketplace app, or from the Marketplace tab of the Agents and Workflows apps.

Layout

registry.yaml                          # the index the marketplace reads
agents/<category>/<name>.yaml
tools/<category>/<name>.yaml
workflows/<category>/<name>.yaml

registry.yaml lists every item with the metadata the marketplace cards show:

version: 2
updatedAt: 2026-08-17
items:
  - kind: agent                                # agent | tool | workflow
    id: agent/coding/code-quality-engineer     # <kind>/<category>/<name>
    installAs: code-quality-engineer           # default local name on install
    displayName: Code Quality Engineer
    description: One line, shown on the card.
    category: Coding
    author: TokenRing Core
    tags: [refactoring, quality]
    version: 1.0.0
    updatedAt: 2026-08-17
    icon: "🧹"
    requiresPlugins: []                        # informational only

An item's id determines its file path: the kind segment becomes the directory (agent → agents/), so agent/coding/code-quality-engineer lives at agents/coding/code-quality-engineer.yaml.

Each item file is exactly the format TokenRing uses for that kind on disk — copy one into .tokenring/agents/, .tokenring/tools/, or .tokenring/workflows/ by hand and it works — plus a kind discriminator and an optional marketplace: block, both of which the installer strips:

kind: agent
marketplace:
  version: 1.0.0
  author: TokenRing Core
  readme: |
    Markdown shown on the item's detail page.
displayName: Code Quality Engineer
description: What this agent is for.
category: Coding
chat:
  systemPrompt: |
    …
  enabledTools:
    - file_*

Contributing

1. Add <kind>s/<category>/<name>.yaml. Categories and names are lowercase with hyphens.
2. Set kind: in the file to match the directory it lives in.
3. Keep prompts portable — no references to a specific repository or private infrastructure.
4. Commit. A pre-commit hook runs bun run generate-index and stages the updated registry.yaml.

After cloning, run bun install (or git config core.hooksPath .githooks) so the hook is active. To rebuild the index by hand:

bun run generate-index

Tools and workflows name the agent they drive via agentType. Say so in the item's readme, so someone installing it knows which agent to install alongside it.

Workflow conventions

Community workflows have to run on someone else's repo. The 15 TokenRing-local files in .tokenring/workflows are this monorepo's automation — they are not the template.

• Discover first. Step 1 surveys language, layout, package manager, and test runner. Do not assume pkg/*, plugin/*, or any other path.
• Natural-language steps on a specialist. Use an agentType that exists under agents/. Do not ship JS globs, /function define js, /tasks write, or approval gates — those need extra plugins and a known tree.
• One job. Audit or implement or plan. The only allowed mix is the quality-review pattern: document findings, then fix only the ones you are confident about.
• Generic artifacts. Write BUGS.md, TECH-DEBT.md, USABILITY.md, and the like at the workspace root (or next to an existing docs directory). Do not invent TokenRing-specific paths.
• Exit cleanly when the surface is missing. A SEO or Docker workflow on a library with neither should say so and stop, not fail.
• Declare the agent in marketplace.readme. Put icon, tags (domain plus audit / implement / plan), and installAs in the marketplace: block so generate-index can build the index from the file.

scripts/generate-index.ts walks agents/, tools/, and workflows/, overlays icon / tags / installAs from each file's marketplace: block (falling back to the previous index), and rewrites registry.yaml. The pre-commit hook runs it on every commit.

Pointing TokenRing at a fork

Set marketplace.baseUrl in your TokenRing configuration to the raw base URL of your registry, e.g. https://raw.githubusercontent.com/<owner>/<repo>/main.