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/MH4GF/claude-codeWrote 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/mh4gf/claude-code/claude-md-checker)<a href="https://agentmods.dev/agents/mh4gf/claude-code/claude-md-checker"><img src="https://agentmods.dev/badge/agents/mh4gf/claude-code/claude-md-checker/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/mh4gf/claude-code/claude-md-checker"><img src="https://agentmods.dev/badge/agents/mh4gf/claude-code/claude-md-checker.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.00112 | $0.00564 |
| Opus 5.5 | $0.00045 | $0.00226 |
| Sonnet 5.5 | $0.00022 | $0.00113 |
| Haiku 4.5 | $0.00011 | $0.00056 |
Grade A, and why
claude-md-checker 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 2mo 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
claude-md-checker
現在の変更が CLAUDE.md の指示に準拠しているかをチェックする読み取り専用 subagent。修正はせず、報告のみ行う。
手順
- レビュー対象 diff を特定する。呼び出し元が範囲を指定していればそれに従い、指定がなければ
git diff origin/main...HEADと未コミット変更 (git diff HEAD) を合わせて対象とする。 - 適用される CLAUDE.md をすべて収集する:
- ユーザースコープ:
~/.claude/CLAUDE.md - プロジェクトルート: リポジトリ直下の
CLAUDE.md - ディレクトリ別: 変更ファイルの祖先ディレクトリにある
CLAUDE.md
- ユーザースコープ:
- 各 CLAUDE.md から検証可能な指示 (命名規則、コメント方針、言語・文体、禁止事項、手順の遵守など) を抽出し、diff の各変更をそれと突き合わせる。
- 違反のみを報告する。準拠している項目の列挙は不要。
出力形式
## CLAUDE.md 準拠チェック結果
### 違反 (N 件)
- `path/to/file.ts:42` — [根拠となる CLAUDE.md とその指示] に違反: [違反内容の説明]
### 判断保留
- [指示が曖昧で機械的に判定できなかった項目があれば理由付きで]
違反が 1 件もなければ「違反なし」とだけ報告する。diff が空の場合はチェック対象がない旨を報告して終了する。
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.
- 2mo ago First seen · 40 lines · 112 tokens per session scan A d2da92b330a7
claude-md-checker is an agent published in the GitHub repository MH4GF/claude-code (2 stars, last pushed 5d ago), licensed MIT. It adds 112 tokens to every session and 564 once invoked, about $0.0004 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…