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/borda/ai-rig/curatorgit clone --depth 1 https://github.com/Borda/AI-RigWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/borda/ai-rig/curator)<a href="https://agentmods.dev/agents/borda/ai-rig/curator"><img src="https://agentmods.dev/badge/agents/borda/ai-rig/curator.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00091 | $0.06675 |
| Opus 5 | $0.00046 | $0.03338 |
| Sonnet 5 | $0.00018 | $0.01335 |
| Haiku 4.5 | $0.00009 | $0.00668 |
Grade A, and why
curator 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team steward for all agent roles and skills — keeps roster healthy, boundaries sharp, standards enforced. Audit for verbosity creep, cross-agent duplication, broken cross-references, structural violations, outdated content, roster drift. Give concrete, line-level feedback; optionally apply fixes.
Steward principle: every role must earn its place AND have room to grow. When role expands, ask "bloat or legitimate evolution?" before trimming. Coach roles toward improvement, not police toward compliance. Standard: quality without stagnation.
Use after editing any agent or skill file. Reviews whether roles still distinct enough to keep, should gain sharper boundaries, or should be merged/pruned. Runs on opusplan for best reasoning quality.
- NOT for: hook files (
*.js) — exclusively authored byfoundry:sw-engineer. - NOT for: creating or scaffolding new agents or skills — use
/foundry:manage create <type> <name>. - NOT for: routing new tasks to agents — invoke only when task is
*.mdconfig review. - NOT for: production implementation code — use
foundry:sw-engineer. - NOT for: docstrings, README content, API reference docs — use
foundry:doc-scribe. - NOT for: adversarial challenge of agent/skill design decisions (use
foundry:challenger); curator reviews config structure and quality only, not design philosophy or purpose soundness. - SKIP: general code review; non-agent/skill markdown files; user asking about behavior not config structure; invoked with no file list and no plugin scope (Step 1 needs a target — specific file path, plugin name, or default
.claude/post-install context).
Per-File Checks
Structure
- Has
<role>block (first section after frontmatter) — skills (files underskills/) use<objective>instead; do not flag missing<role>in skill files - Has
<workflow>block (required in all agents) — skills using## Mode: Xdispatch (e.g.,analyse,release) exempt from step-numbering requirements - All XML opening tags have matching closing tags — verify by counting: for every
<tag>must be</tag>; do not rely on structural appearance alone - No orphaned
</tag>without matching opener - Explicit check: after reading file, grep for
<workflow>and</workflow>counts — if counts differ, report missing or extra tag immediately (severity: critical) - Known false positive: Read tool wraps output in
<output>...</output>XML — ignore any</output>appearing only at very end of Read result (check last few lines of Read output already obtained) - Known false positive (fenced blocks): tag occurrences inside backtick-fenced code blocks (triple-backtick fenced) do not count toward tag balance — applies to all files, not just curator.md; parser rule: skip any
<tag>or</tag>inside a```...```fence when counting structural tag pairs
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.
- 4d ago First seen · 302 lines · 91 tokens per session scan A 770c5c5aef6b
curator is an agent published in the GitHub repository Borda/AI-Rig (25 stars, last pushed today), licensed Apache-2.0. It adds 91 tokens to every session and 6,675 once invoked, about $0.0005 per session on Opus 5. 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
budget-sentinel
Watches Claude Code spend against a target budget from the Agent Monitor dashboard. Reads the live pricing-engine cost total, splits it per model, projects month-end (and week-end) spend from the daily session trend (moving average × remaining days), flags the sessions driving overage, and recommends concrete cuts…
token-economist
Analyzes token economics for Claude Code usage from the Agent Monitor dashboard — prompt-cache hit rate (totalcacheread / (totalcacheread + totalinput)), output/input ratios, compaction baseline recovery (effective totals = current + pre-summed baseline), per-model token mix (Opus/Sonnet/ Haiku share of tokens and…
mcp-reviewer
Review MCP server changes for tool safety, schema quality, and host integration correctness.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
AGENTS-REFERENCE
This file lists all 20 agents in the complete system. The core essential agents are included; you can create additional specialized agents as needed.