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/weekly-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/weekly-plan)<a href="https://agentmods.dev/commands/amey-thakur/claude-certifications/weekly-plan"><img src="https://agentmods.dev/badge/commands/amey-thakur/claude-certifications/weekly-plan/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/weekly-plan"><img src="https://agentmods.dev/badge/commands/amey-thakur/claude-certifications/weekly-plan.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.00000 | $0.00366 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
weekly-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 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
Produce one week of study for the certification in $ARGUMENTS.
Gather what is missing
Ask for the certification, which week of preparation this is, and the hours available, unless a plan or diagnostic earlier in this session already established them. Use what is already known rather than asking again.
Build
Read the certification's README.md, notes.md, and guide/study-strategy.md, plus guide/courses.md for the material that teaches each objective.
Lay out the week as dated sessions, each with:
- A duration that fits the stated hours, in blocks a person will actually sit through rather than idealised marathons
- One specific objective or small group of objectives from the blueprint, named exactly as the guide names them
- The specific material for it: the course lesson, documentation page, or article, linked from the repository's pages rather than described vaguely
- A concrete output for the session, so completion is verifiable: notes written, a schema designed, an agent loop running, a domain drilled to a stated score
Include across the week:
- At least one hands-on session that advances the build task from the plan
- One
/cert:drillon the weakest domain - A closing
/cert:mockor/cert:score-checkto measure the week
Front-load the heaviest blueprint domains early in the week when energy is highest, and put review at the end. If the hours are too few for the objectives targeted, cut objectives and say which were cut, rather than compressing everything into sessions that cannot be completed.
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 · 30 lines · 0 tokens per session scan A d83ac2de7e8c
weekly-plan is a command published in the GitHub repository Amey-Thakur/CLAUDE-CERTIFICATIONS (20 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 366 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.