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.
git clone --depth 1 https://github.com/Nmor/the-claude-councilWrote 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/nmor/the-claude-council/doc-updater)<a href="https://agentmods.dev/agents/nmor/the-claude-council/doc-updater"><img src="https://agentmods.dev/badge/agents/nmor/the-claude-council/doc-updater/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nmor/the-claude-council/doc-updater"><img src="https://agentmods.dev/badge/agents/nmor/the-claude-council/doc-updater.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00050 | $0.01913 |
| Opus 5 | $0.00025 | $0.00957 |
| Sonnet 5 | $0.00010 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
doc-updater 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 9d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 196 lines · 50 tokens per session scan A e337406238ac
doc-updater is an agent published in the GitHub repository Nmor/the-claude-council (9 stars, last pushed 2d ago), with no licence file. It adds 50 tokens to every session and 1,913 once invoked, about $0.0003 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-31.
Other agents, from other repositories
code-quality-reviewer
Use this agent when you need comprehensive manual quality review, integration testing, and user experience validation. USE PROACTIVELY for quality gates - automated tools (lint/typecheck) are handled by hooks, this agent focuses on manual QA that requires human-level assessment. Examples: Context: User has just…
file-refactor-organizer
Use this agent when you need to break down large files into smaller, more maintainable components or modules. This agent should be used when files exceed 300 lines, when code organization needs improvement, or before committing changes to ensure proper file structure. Examples: Context: User has a large React…
brownfield-accuracy-judge
Evaluates how accurately an implementation plan accounts for existing code — correctly identifying what to modify vs create, avoiding reimplementation, and finding the right integration points.
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
evolve-error-handling-scan
Silent-failure adversary for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on bugfix cycles — and on any large diff regardless of goal type — to hunt swallowed errors, ignored return values, and catch-all fallbacks in the changed code. BLOCKS when a failure path is silenced so it…