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 skills add ArcticFox2029/chamnan --skill whygit 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/skills/arcticfox2029/chamnan/why)<a href="https://agentmods.dev/skills/arcticfox2029/chamnan/why"><img src="https://agentmods.dev/badge/skills/arcticfox2029/chamnan/why/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/skills/arcticfox2029/chamnan/why"><img src="https://agentmods.dev/badge/skills/arcticfox2029/chamnan/why.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.00658 |
| Opus 5.5 | $0.00018 | $0.00263 |
| Sonnet 5.5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
why 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 23d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your machine, or your code — decide that first
The expensive mistake is not picking the wrong fix. It is spending two hours in the code when the problem was a version, or two hours on the environment when the problem was a line somebody changed. One decision comes before any debugging, and this repository holds evidence for both sides of it.
1 · The machine
chamnan-env
What this repository has declared about the environments it runs in — the constraints nobody writes down and everybody re-learns. A shell alias that hangs without a terminal, a binary that is not on this platform, a Python whose certificate bundle is broken. If the failure matches one of these, stop: there is nothing wrong with the code.
An error that mentions a command not found, a version mismatch, a certificate, a path separator or a permission is a machine failure until something rules that out.
2 · The code
chamnan-impact <the file the failure points at>
Who imports it, which tests cover it, and what this repository has recorded about it. If the failing test is in that list, the change and the failure are connected. If it is not, the error's file and the failure's cause are probably different files.
3 · What this cannot tell you, and do not pretend otherwise
chamnan does not know when the test last passed. A Bash tool response carries no exit code —
only stdout, stderr and whether it was interrupted — and the stderr field was measured to be a
constant rather than a signal, so there is no record of outcomes to consult. git log on the files
chamnan-impact names is the substitute, and it is a weaker one: it shows what changed, not what
broke.
Say that plainly rather than inventing a history.
When the agent already knows
If you just edited the file the failure names, this adds nothing — you have the diff and the error, which is more than either command above can give you. Use it when the failure is one you did not cause: a test that was already red when the session opened, a failure in code you did not touch, or one that appeared after pulling somebody else's work.
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.
- 23d ago First seen · 61 lines · 46 tokens per session scan A d1d10576a0c0
why is a skill published in the GitHub repository ArcticFox2029/chamnan (10 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 658 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-09-23.
Other skills, from other repositories
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
cloudflare-workers-observability
Cloudflare Workers observability with logging, Analytics Engine, Tail Workers, metrics, and alerting. Use for monitoring, debugging, tracing, or encountering log parsing, metric aggregation, alert configuration errors.
cloudflare-workers-dev-experience
Cloudflare Workers local development with Wrangler, Miniflare, hot reload, debugging. Use for project setup, wrangler.jsonc configuration, or encountering local dev, HMR, binding simulation errors.
cloudflare-workers-performance
Cloudflare Workers performance optimization with CPU, memory, caching, bundle size. Use for slow workers, high latency, cold starts, or encountering CPU limits, memory issues, timeout errors.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.