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/ncoevoet/claude-markdown-health-checkWrote 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/plugins/ncoevoet/claude-markdown-health-check/plugin)<a href="https://agentmods.dev/plugins/ncoevoet/claude-markdown-health-check/plugin"><img src="https://agentmods.dev/badge/plugins/ncoevoet/claude-markdown-health-check/plugin/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/plugins/ncoevoet/claude-markdown-health-check/plugin"><img src="https://agentmods.dev/badge/plugins/ncoevoet/claude-markdown-health-check/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
markdown-health-check 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 12d 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
{
"name": "markdown-health-check",
"displayName": ".claude/ Health Check",
"version": "0.20.0",
"description": "Audits the .claude/ ecosystem — skills, commands, hooks, agents, settings, plugins, memory — for dead references, weak triggers, token bloat, dormant skills, permission drift, hook reliability, memory hygiene, and context bloat. Evidence-grounds every judgment finding before reporting.",
"author": {
"name": "Nicolas Coevoet"
},
"homepage": "https://github.com/ncoevoet/claude-markdown-health-check",
"repository": "https://github.com/ncoevoet/claude-markdown-health-check",
"license": "MIT",
"keywords": [
"claude-code",
"skills",
"audit",
"health-check",
"linter",
"command",
"usage",
"telemetry",
"permissions",
"memory"
]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 78 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 12d ago Changed 0dc9b74adae4
- 1mo ago Changed a2ec23f53be2
- 1mo ago Changed aec872bc8c36
- 1mo ago First seen · 25 lines scan A ec28ab6a3745
markdown-health-check is a plugin published in the GitHub repository ncoevoet/claude-markdown-health-check (47 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
distributed-debugging
Distributed system tracing and debugging across microservices.
distributed-debugging
Distributed system tracing and debugging across microservices.
agent-chat-plugin
Peer AI agents coordinate through markdown messages in shared channel folders — group chat / blackboard, no orchestrator, autonomous zero-token waiting, cross-platform.
aio-golang-mastery
Write and lint idiomatic Go end-to-end — a 7-tool lint chain (build, vet, golangci-lint, govulncheck, nilaway, deadcode, race) plus reference-grade patterns for concurrency, errors, generics, gRPC, naming/style enforcement (revive 21-rule set, golangci-lint v2 production config), and production hardening.
aio-ios-device-debug
Debug iOS apps on physical devices. Build, install, launch, capture logs, pull crash reports, and analyze crashes from the terminal.
menhera-loop
Menhera-style Claude Code progress messages focused on missing requirements, verification, and hidden TODOs.