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 instructions/jamesdsizemore/headcleaner-cli/claude-mdgit clone --depth 1 https://github.com/jamesdsizemore/headcleaner-cliWrote 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/instructions/jamesdsizemore/headcleaner-cli/claude-md)<a href="https://agentmods.dev/instructions/jamesdsizemore/headcleaner-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/jamesdsizemore/headcleaner-cli/claude-md.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.00578 | $0.00578 |
| Opus 5 | $0.00289 | $0.00289 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
headcleaner-cli CLAUDE.md 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 3d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Repository discipline
- Work only inside this repository. Do not commit, push, merge, reset, or rewrite history unless the user explicitly asks.
- Preserve existing user work. Inspect Git status before edits; change only the requested scope.
- Use RTK for bounded Git/diff evidence, Graft for symbol/caller tracing, and context-mode for plans, contracts, and documentation seams before edits and at final review.
- The mandatory test command is
unset PYTHONPATH && uv run --no-sync --python 3.13 pytest. Focused runs may append test paths or pytest flags. - Never auto-claim human review of converted output. Preserve
status: unverifiedandverified: human:pendingdefaults.
Required development records
For every multi-step task, create or update a local plan under .plans/ before implementation. .plans/ is ignored and contains working context only.
Keep these tracked records current during development:
BACKLOG.md— scoped work, acceptance evidence, documentation impact, and non-goals.ISSUES.md— real defects and recoveries; archive, do not delete.MEMORY.md— stable repository conventions only; never secrets or transient output.DEVELOPMENT_HISTORY.md— phase and commit evidence.DEPENDENCIES.mdandPINS.md— dependency intent, compatibility pins, and lock verification.
Non-negotiable documentation gate
“Docs updated” means the entire active documentation surface was considered: root README.md plus every Markdown page under docs/, excluding docs/_archive/ and the historical docs/plans/archive/.
For every phase:
- Create an exhaustive audit with
uv run --no-sync --python 3.13 python scripts/verify_docs.py --write-audit-template <phase>. - Update every pertinent page. For every remaining page, record
reviewedornot-applicablewith a concrete evidence statement indocs/development/phase-audits/<phase>.json. - Run
uv run --no-sync --python 3.13 python scripts/verify_docs.py --phase <phase>. - Do not state that the phase is complete until the audit, links/anchors, focused tests, full suite, and final Git review pass.
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.
- 3d ago First seen · 41 lines · 578 tokens per session scan A d0286c9f14ee
headcleaner-cli CLAUDE.md is an instructions file published in the GitHub repository jamesdsizemore/headcleaner-cli (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 578 tokens to every session, about $0.0029 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.