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/prep-plan.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/prep-plan)<a href="https://agentmods.dev/commands/amey-thakur/claude-certifications/prep-plan"><img src="https://agentmods.dev/badge/commands/amey-thakur/claude-certifications/prep-plan.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.1 | $0.00000 | $0.00420 |
| Opus 5 | $0.00000 | $0.00210 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
prep-plan 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 8d 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
Build a preparation plan for the certification in $ARGUMENTS.
Gather what is missing
Ask only for what was not supplied, in one message rather than one question at a time: the certification, hours available per week, target exam date if any, current experience with the technologies in the blueprint, and whether a /cert:diagnostic has been run. If a diagnostic was run in this session, use its domain scores instead of asking about experience.
Build
- Read the certification's
README.md(blueprint and weights),notes.md(what matters within each domain), andguide/study-strategy.md(the method and per-exam emphasis). - Read
guide/courses.mdfor the official courses that teach each area, andguide/resources.mdfor documentation and videos.
Produce a plan with:
- Scope. The blueprint as a checklist of objectives, ordered by exam weight, with the candidate's confidence marked where known.
- Sequence. Which courses, documentation, and engineering articles to work through, and in what order. Weight time by domain percentage, not by personal interest: name explicitly where the heaviest domains are.
- Build task. The one thing to build with their own hands, taken from the certification's preparation section. This is not optional; every official guide asks for it.
- Checkpoints. Where in the schedule to run
/cert:drilland/cert:mock, and what score to expect at each before proceeding. - Fit to the calendar. Translate all of the above into their stated hours per week and target date. If the date is not achievable at that pace, say so plainly and give the two options: move the date or raise the hours.
Close by offering /cert:weekly-plan for the next week in detail.
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.
- 8d ago First seen · 26 lines · 0 tokens per session scan A 89561a583504
prep-plan is a command published in the GitHub repository Amey-Thakur/CLAUDE-CERTIFICATIONS (19 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 420 tokens. 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.