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.
npx agentmods add agents/monkilabs/opencastle/agent-registrygit clone --depth 1 https://github.com/monkilabs/opencastleWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00468 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
agent-registry 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 2d 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.
What it actually says
# Agent Registry
Project-specific agent tiers and scope examples referenced by the `team-lead-reference` skill.
<!-- Populated by `opencastle init` based on project structure. -->
## Specialist Agent Registry
Tiers describe what kind of model the work wants. Your assistant picks the actual
model — it knows which ones your account can reach and what they cost today.
| Agent | Tier | Best For |
|-------|------|----------|
| **Team Lead** | Premium | Decomposing work, delegating, verifying results |
| **Architect** | Premium | Architecture decisions, ADRs, critical review |
| **Security Expert** | Premium | Auth, access policies, headers, input validation |
| **Developer** | Standard | Features, pages, components, routing, API routes and contracts |
| **UI/UX Expert** | Standard | Components, styling, accessibility, frontend design |
| **Data Engineer** | Standard | Migrations, access policies, query performance, ETL pipelines, imports |
| **Content Engineer** | Standard | CMS schema, content types, content queries |
| **Testing Expert** | Standard | E2E and integration tests, browser validation |
| **Performance Expert** | Standard | Bundle size, Core Web Vitals, profiling |
| **DevOps & Release** | Standard | Deployments, CI/CD, cron jobs, pre-release verification, changelogs |
| **Researcher** | Standard | Codebase exploration, pattern discovery, git archaeology |
| **Writer** | Economy | UI copy, error messages, docs, roadmaps, meta tags, structured data |
| **Reviewer** | Economy | Fast review after every delegation |
## Deepen-Plan Scope Examples
<!-- Customize these paths to match your project structure.
When running the Deepen-Plan protocol, split research by domain: -->
```
Researcher A: "Research database/backend aspects of [feature]"
Scope: <database-migrations-dir>/, <server-libs>/
Researcher B: "Research frontend/UI aspects of [feature]"
Scope: <ui-libs>/, <app-dir>/
Researcher C: "Research CMS/content aspects of [feature]"
Scope: <cms-dir>/, <queries-lib>/
```
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.
- 2d ago First seen · 46 lines · 0 tokens per session scan A c4577b4caf4f
agent-registry is an agent published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 468 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.
Other agents, from other repositories
openagent
Your intelligent assistant for questions, tasks, and workflows.
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
repo-manager
Agent ID: repo-manager Category: Meta Type: Meta Agent Version: 2.0.0 Status: Stable.
opencoder
Your expert development partner for complex coding tasks.
context-scout
Discover relevant context files, coding standards, and project conventions. Use before implementation begins to find the right standards to follow. Examples: Context: User wants to build a new authentication feature. user: "Build me a JWT authentication system" assistant: "Before implementing, I'll use context-scout…
category-system
Version: 2.0.0 Status: Active Last Updated: 2025-12-09.