Community Agents

Browse ready-to-use agents from the community repository, or share your own subagents and primary agents with other developers.

Community Repository

Don't want to start from scratch? Browse ready-to-use agents created by the community:

Available Agents

The community repository includes agents such as:

• code-reviewer — A subagent that reviews diffs for bugs and style issues with read-only tool access
• docs-writer — Drafts and updates documentation from the surrounding codebase
• test-runner — Runs the test suite and summarizes failures

Using Community Agents

1. Browse the agents directory
2. Find an agent that matches your needs
3. Click on the JSON file to view it
4. Click "Raw" to get the raw JSON, or download the file
5. In SuperClawd, go to Agents → Import
6. Paste the JSON or drag and drop the file
7. Click Import Agent

Contributing Your Agents

Have agents that pull their weight? Share them with the community:

1. Export your agent as JSON from the agent card menu
2. Fork the community repository
3. Add your agent JSON file to agents/examples/
4. Update agents/README.md to list your agent
5. Submit a pull request

Agent JSON Format

Community agents follow this structure — identity plus configuration content only (no workspace ids, enabled state, counts, or version pointers):

{
  "name": "code-reviewer",
  "description": "Reviews diffs for bugs and style issues",
  "vendor": "anthropic",
  "model": "claude-opus-4-8",
  "prompt": "You are a meticulous code reviewer. Inspect the diff for correctness, security, and style issues, then report concise, actionable findings.",
  "mode": "subagent",
  "tools": {
    "read": "allow",
    "glob": "allow",
    "grep": "allow",
    "edit": "deny",
    "write": "deny",
    "bash": "deny",
    "webfetch": "deny",
    "task": "deny"
  },
  "steps": 50
}

Contribution Guidelines

• Use kebab-case for agent names, at most 30 characters (e.g., code-reviewer)
• Keep descriptions under 250 characters
• Set mode to either subagent or primary
• Use a supported vendor (e.g., anthropic) and a valid model for it
• Set each entry in tools to allow, deny, or ask — grant only the access the agent needs
• Keep steps between 1 and 1000 (or null for no limit), and the prompt within the platform limit
• Test your agent before submitting

Sharing via Links

Instead of a JSON file, you can hand someone an unlisted, revocable share link straight from an agent's menu. The recipient can preview the agent and import their own copy into another workspace.

• A stable release is required. You can only create a share link once the agent has been published and promoted to a stable release.
• Pinned or live. A pinned link freezes a specific version; a live link always follows your current stable release.
• Optional expiry & max-imports. Set an expiration date and an import limit; open and import counts are tracked (no importer identity).
• Revocable. Delete the link at any time to cut off further imports.

Like a JSON import, importing from a share link creates a new, independent enabled copy (auto-renamed on name collision) that must be published and promoted before it's available to your team's stable CLI sessions.

See the Contributing Guide for detailed instructions.