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/martinwickman/ccmonitor/claude-mdgit clone --depth 1 https://github.com/MartinWickman/ccmonitorWrote 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/martinwickman/ccmonitor/claude-md)<a href="https://agentmods.dev/instructions/martinwickman/ccmonitor/claude-md"><img src="https://agentmods.dev/badge/instructions/martinwickman/ccmonitor/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.00277 | $0.00277 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade B, and why
ccmonitor CLAUDE.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Never modify `~/.claude/settings.json`** during development. Use `.claude/settings.local.json` (project-scoped, gitignored) for testing hooks. What it actually says
ccmonitor
A monitoring tool for tracking multiple concurrent Claude Code instances across projects.
ccmonitor uses Claude Code hooks to collect status data from all running instances and displays them in a single live-updating view.
Development guidelines
- Never modify
~/.claude/settings.jsonduring development. Use.claude/settings.local.json(project-scoped, gitignored) for testing hooks. - Both the hook handler and monitor must support a
CCMONITOR_SESSIONS_DIRenvironment variable that overrides the default~/.ccmonitor/sessions/path. Use this to point at a local test directory during development. - Use fake session files to test the monitor UI without needing live Claude Code sessions.
- Don't git commit unless told to!
- To parse and see the output, you can run the command with
ccmonitor --onceto just have it run, print the output and then exit. - Run unit tests
- Update the @TODO file to keep track.
Key files
- @PRD.md — Product requirements
- @ARCHITECTURE.md — Architecture decisions, data flow, session file schema, tech stack
- @TODO.md - Progress and what to do next. Update this as you progress
- GO_BEST_PRACTICES.md - READ THIS WHEN WRITING GO PROGRAMMING LANGUAGE CODE
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 · 23 lines · 277 tokens per session scan B fa7c9f640d49
ccmonitor CLAUDE.md is an instructions file published in the GitHub repository MartinWickman/ccmonitor (2 stars, last pushed 6mo ago), licensed MIT. It adds 277 tokens to every session, about $0.0014 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
claude-code-config-switcher CLAUDE.md
Instructions for guyskk/claude-code-config-switcher, covering 项目背景, 开发流程, 特别说明：你要使用中文, write idiomatic go code and 提交前检查.
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.
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).