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 skills add qwerfunch/cladding --skill doctorgit clone --depth 1 https://github.com/qwerfunch/claddingWrote 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/skills/qwerfunch/cladding/doctor)<a href="https://agentmods.dev/skills/qwerfunch/cladding/doctor"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/doctor/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/skills/qwerfunch/cladding/doctor"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00093 | $0.00857 |
| Opus 5.5 | $0.00037 | $0.00343 |
| Sonnet 5.5 | $0.00019 | $0.00171 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
doctor 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 1mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cladding doctor
Run clad doctor from the project root. The verb is observability — it never mutates the working tree.
--cwd <path>— read events from a project directory other than the current one (default cwd).--json— emit the rawDoctorReportshape instead of the formatted text surface; the additive shape ({cwd, events, sentinelMiss, governance, hooks, ciVersion}) is the stable wire format for MCP clients and follow-up tooling.
The text surface prints:
- One pulse line with total events and total sentinel-miss count (
passwhen zero misses,noteotherwise). - An event-type breakdown line (one
<type>=<count>token per non-zeroEventType). - Claude Code hook health: whether the runtime has actually been observed, whether the observed engine version matches the current CLI, and the last firing time (or
never observed) for session start, prompt submit, before edit, after edit, and session stop. - A non-blocking CI warning naming each GitHub Actions workflow that invokes an unversioned or floating
npx claddingpackage. Numeric selectors such as[email protected]and[email protected]stay quiet. - Governance counts for gate runs, done attempts and rejections, stop blocks, known-failing Stop exits, blocked fingerprints reproduced by a later gate, and attestation state.
- When sentinel-miss events exist:
by phase/by cause/by fallbackaggregates from the v0.3.39 telemetry payload.- Top-5 missed sentinels (
CONVENTIONS_MD/ARCHITECTURE_YAML/SCENARIO_FLOWS/CAPABILITIES_YAML/WHY/WHAT/PURPOSE) sorted by count desc, name asc. - Last 3 unique dispatcher error strings (most recent first; errors are truncated to 200 chars at the emit site).
- A one-line tuning hint.
Exit codes
0— events.log was either missing (greenfield) or readable. A greenfield workspace prints a friendly note and exits 0; a healthy host with zero misses also exits 0 with apassline.1—events.log.jsonlexists but cannot be parsed as JSONL (corrupt telemetry).
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.
- 1mo ago Changed fb0dc8d1b8b1
- 1mo ago First seen · 45 lines · 93 tokens per session scan A e530159f5d3a
doctor is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 857 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-30.
Other skills, from other repositories
bug-fix-protocol
8-step disciplined bug-fix protocol that treats every production bug as two failures — the code defect itself and the testing system that allowed it through. Use when fixing a production bug, investigating a regression, writing a post-mortem, or auditing a missed defect. Triggers on "fix this bug", "production bug"…
vibedrift-drift-check
Use when writing or changing code in an existing repository to keep new code consistent with the repo's own conventions and avoid duplicating code that already exists. Checks a proposed function against the repo's dominant patterns and existing functions BEFORE it lands, turning drift detection into drift prevention.…
debugger
Systematic debugging method: 5-step root-cause analysis (capture, isolate, hypothesize, investigate, fix & verify) plus common bug-pattern reference. Use when errors, exceptions, test failures, or unexpected behavior appear. Loaded automatically by the debugger agent.
mcp-check
Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
debug
Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.
project-health-check
Audit project health across 7 dimensions (documentation, test coverage, security, code quality, dependencies, database, build/deploy) producing a scored report with prioritized fixes. Use for periodic checkups, before releases, or when the user runs /project-health-check.