category-system

A way to organize coding agents into a hierarchy of general coordinators, category specialists, and smaller delegated helpers. Agents are grouped by areas such as development, content, and data.

In plain words
What is it for?
Use it to design or maintain an agent directory with core agents, domain specialists, and subagents for tasks such as frontend development, backend work, writing, or data analysis.
Why use it?
It gives a large collection of agents a predictable structure, making specialists easier to find and maintain. It also clarifies which agent coordinates work and which agent handles a specific task.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/darrenhinde/openagentscontrol/category-system
Clone the repo
git clone --depth 1 https://github.com/darrenhinde/OpenAgentsControl
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,495 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02495
Opus 5 $0.00000 $0.01247
Sonnet 5 $0.00000 $0.00499
Haiku 4.5 $0.00000 $0.00249

Measured 3d ago against content hash 971827f99d6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

category-system scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

docs/agents/category-system.md · 455 lines

How it starts

The opening of the file, as written. The whole thing — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Category-Based Agent System

Version: 2.0.0
Status: Active
Last Updated: 2025-12-09


🎯 Overview

The category-based agent system organizes agents into logical categories, making it easier to discover, contribute, and maintain domain-specific agents.

Key Concepts

Three-Tier Hierarchy:

  1. Core Agents - Primary agents users interact with (orchestrator, coder)
  2. Category Agents - Domain-specific specialists (frontend, copywriter, etc.)
  3. Subagents - Delegated specialists called by core/category agents (tester, reviewer, etc.)

📁 Directory Structure

.opencode/agent/
├── core/                    # Core Agents (System-level)
│   ├── openagent.md         # Universal coordinator
│   └── opencoder.md         # Development specialist
│
├── meta/                    # Meta-level Agents
│   └── system-builder.md    # System architect
│
├── development/             # Development Specialists
│   ├── frontend-specialist.md
│   ├── backend-specialist.md
│   ├── devops-specialist.md
│   └── codebase-agent.md
│
├── content/                 # Content Creation
│   ├── copywriter.md
│   └── technical-writer.md
│
├── data/                    # Data & Analysis
│   └── data-analyst.md
│
├── product/                 # Product & Strategy
│   └── (empty - ready for contributions)
│
├── learning/                # Education & Coaching
│   └── (empty - ready for contributions)
│
└── subagents/              # Delegated Specialists
    ├── code/               # Code-related
    ├── core/               # Core workflow
    ├── system-builder/     # System generation
    └── utils/              # Utilities

🔧 Using Category Agents

Installation

# Install all development agents
./install.sh developer

# Install specific profile
./install.sh full

Running Tests

cd evals/framework

# Test core agent
npm run eval:sdk -- --agent=core/openagent

# Test category agent
npm run eval:sdk -- --agent=development/frontend-specialist

# Test subagent
npm run eval:sdk -- --agent=TestEngineer

Read the full file on GitHub · 455 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 455 lines · 0 tokens per session scan A 971827f99d6f

Subscribe to this mod's changes

category-system is an agent published in the GitHub repository darrenhinde/OpenAgentsControl (4,815 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,495 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

ralph-loop-runner

Use this agent when you need to execute a Ralph orchestration loop end-to-end and verify its completion. This includes testing prompts against the Ralph system, validating that orchestration completes successfully, and capturing both results and any runtime issues. Examples:\n\n \nContext: User wants to test if a…

mikeyobrien/ralph-orchestrator · 286 tokens

chaos-monkey

You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.

WrongStack/WrongStack · 0 tokens

23-learning-development

You are the Head of L&D building the learning infrastructure that keeps the entire organization sharp, current, and growing. A company that stops learning stops winning. You design training programs, build knowledge systems, and ensure every person — from new intern to founding CEO — is continuously developing.

ankitjha67/product-architect · 0 tokens

35-user-research

You are the Head of User Research & Insights. You are the company's source of truth about who the user actually is, what they are trying to get done, and why your product does or does not help them. You run rigorous generative and evaluative research, you protect study quality against bias, and you turn raw…

ankitjha67/product-architect · 0 tokens

44-investor-relations

You are the Head of Investor Relations. You own the ongoing narrative to the people who fund the company and the relationships behind it. Governance & IPO (Agent 26) builds the machinery of being a company investors can own; Finance (Agent 18) produces the numbers; you turn those numbers into a story investors…

ankitjha67/product-architect · 0 tokens

45-corporate-development

You are the Head of Corporate Development. You own inorganic growth — the things the company buys, invests in, or sells rather than builds: acquisitions, minority investments, joint ventures, and divestitures. Where BD & Partnerships (Agent 33) owns contractual growth (deals where two companies stay separate and…

ankitjha67/product-architect · 0 tokens