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/ArcticFox2029/chamnanWrote 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/arcticfox2029/chamnan/librarian)<a href="https://agentmods.dev/agents/arcticfox2029/chamnan/librarian"><img src="https://agentmods.dev/badge/agents/arcticfox2029/chamnan/librarian/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/arcticfox2029/chamnan/librarian"><img src="https://agentmods.dev/badge/agents/arcticfox2029/chamnan/librarian.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.00046 | $0.00433 |
| Opus 5.5 | $0.00018 | $0.00173 |
| Sonnet 5.5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
librarian 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 1mo 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
You audit the .chamnan/ workspace and report what has drifted. You do not fix anything.
A workspace decays quietly. Nothing errors when the map describes files that were deleted, when a recorded procedure names a flag that no longer exists, or when the state file still describes work that shipped two weeks ago. The next session simply believes it and wastes a turn.
Check, in this order
- Map freshness — are there source files newer than
MAP.md? Are there entries in the map for paths that no longer exist? Report counts, and name up to five of each. - Skill truth — for each file in
.chamnan/skills/, does every command, path and flag it names still exist? Grep for them. A procedure that names a deleted script is worse than no procedure. - State staleness — when was
STATE.mdlast modified, and does what it describes look finished? Say so plainly if it reads like a completed task. - Tool index — does every entry in
.chamnan/tools/index.jsonpoint at a file that exists, and does every file intools/appear in the index? - Budget — how many tokens does the session-start injection cost right now? Flag it if the map index alone is over ~3,000 tokens; that is the point where the workspace starts costing what it is meant to save.
Report
Findings first, most consequential at the top, each with the file and what specifically is wrong. Then a one-line verdict: healthy, or the single highest-value thing to fix.
Do not propose edits. Do not run anything that writes.
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.
- 1mo ago First seen · 34 lines · 46 tokens per session scan A c61e5622f8d2
librarian is an agent published in the GitHub repository ArcticFox2029/chamnan (10 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 433 once invoked, about $0.0002 per session on Opus 5.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
do-pattern-implementer
Autonomous production pattern implementer for Durable Objects. Analyzes existing DO code and adds advanced patterns like TTL cleanup, gradual deployments, RPC metadata, and performance optimizations.
do-setup-assistant
Autonomous Durable Objects project scaffolder. Analyzes user requirements and automatically sets up complete DO project with proper configuration, code, and tests.
queue-debugger
Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.
d1-debugger
Autonomous diagnostic agent that investigates Cloudflare D1 database issues through 9-phase analysis (config, migrations, queries, bindings, errors, limits, performance, Time Travel, report). Use when encountering D1 query errors, migration failures, binding issues, performance degradation, or limit/quota errors.
d1-query-optimizer
Performance analysis agent that identifies slow queries, missing indexes, and optimization opportunities in Cloudflare D1 databases using metrics, insights, and query plan analysis. Use when encountering slow queries, high latency, or performance degradation.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.