Borrowing it
Nothing to install: this file belongs to Amey-Thakur/CLAUDE-CERTIFICATIONS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Amey-Thakur/CLAUDE-CERTIFICATIONS/main/.claude/commands/cert/diagnostic.mdgit clone --depth 1 https://github.com/Amey-Thakur/CLAUDE-CERTIFICATIONSWrote 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/commands/amey-thakur/claude-certifications/diagnostic)<a href="https://agentmods.dev/commands/amey-thakur/claude-certifications/diagnostic"><img src="https://agentmods.dev/badge/commands/amey-thakur/claude-certifications/diagnostic/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/commands/amey-thakur/claude-certifications/diagnostic"><img src="https://agentmods.dev/badge/commands/amey-thakur/claude-certifications/diagnostic.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.00016 | $0.00340 |
| Opus 5 | $0.00008 | $0.00170 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
diagnostic 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 9d 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
Run a diagnostic assessment for the certification named in $ARGUMENTS. If no certification was given, ask which of the four they are preparing for and stop until they answer.
Prepare
- Read that certification's
README.mdfor the blueprint: domains, weights, objectives. - Read
question-bank.jsonat the repository root and select that exam's questions.
Run
Ask 12 questions drawn across every domain, allocated by blueprint weight so heavy domains get more items. Shuffle the option order for each question. Present one question at a time and wait for an answer before continuing. Do not reveal whether an answer was right until the end: this is a measurement, not a lesson.
If the bank has fewer questions than a domain's allocation needs, write additional ones in the same style, grounded strictly in that domain's published objectives.
Report
Produce a readiness profile:
- Overall score, and how it maps to the readiness bands in the certification's
mock-exam-1.md - A table of every domain: questions asked, correct, and the domain's exam weight
- Weak domains, ranked by the product of error rate and exam weight, so the ranking reflects what will actually cost marks
- For each weak domain, the two or three specific objectives from the blueprint that the missed questions map to
Close by recommending the next step: /cert:drill for a weak domain, or /cert:prep-plan if several domains are weak.
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.
- 9d ago First seen · 29 lines · 16 tokens per session scan A 3b3d55aa246c
diagnostic is a command published in the GitHub repository Amey-Thakur/CLAUDE-CERTIFICATIONS (20 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 340 once invoked, about $0.0001 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 commands, from other repositories
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.
doc-explain
Command "doc-explain" from christopherlouet/claude-base, covering explain agent, code to explain, objective, workflow and expected output.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
security-scan
Run security audit on codebase.
help
Explain Ralph Wiggum technique and available commands.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.