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/scottrigby/claudeman/claude-mdgit clone --depth 1 https://github.com/scottrigby/claudemanWrote 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/scottrigby/claudeman/claude-md)<a href="https://agentmods.dev/instructions/scottrigby/claudeman/claude-md"><img src="https://agentmods.dev/badge/instructions/scottrigby/claudeman/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.00381 | $0.00381 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
claudeman 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 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.
What it actually says
Claudeman Development
Documentation Files
- README.md — user-facing install, usage, and migration reference
- ARCHITECTURE.md — design decisions, data flows, and "why" explanations for non-obvious choices
- ROADMAP.md — future enhancement ideas organized by category; uses
- [ ]checkboxes for actionable items - CLAUDE.md (this file) — dev workflow instructions for Claude sessions (testing, git policy)
Testing
If developing from inside a container (e.g., via claudeman itself), run
npm install first — native modules like vitest's rolldown binding are
platform-specific and need to be rebuilt for the container's architecture.
Tests are split into three tiers:
npm test # unit — fast, offline, runs in containers
npm run test:integration # integration — needs network (containers.dev API)
npm run test:e2e # e2e — needs container runtime (podman/docker) + network
npm run test:all # all tiers
File naming convention:
*.test.js— unit tests*.integration.test.js— network-dependent tests*.e2e.test.js— container runtime tests (future)
For a quick smoke test of the CLI:
./claudeman help
./claudeman feature search go
./claudeman profile list
./claudeman migrate --help
To test notifications manually (requires two terminals on host):
# Terminal 1
./claudeman listen
# Terminal 2
node lib/notify.js complete "test"
Git Policy
- Read-only git commands are allowed
- Any git command that modifies the Git state requires explicit user permission
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 · 54 lines · 381 tokens per session scan A 0ccb7f3fb589
claudeman CLAUDE.md is an instructions file published in the GitHub repository scottrigby/claudeman (20 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 381 tokens to every session, about $0.0019 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 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.