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/afaizalam2003/Master-claude-skillWrote 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/afaizalam2003/master-claude-skill/review)<a href="https://agentmods.dev/commands/afaizalam2003/master-claude-skill/review"><img src="https://agentmods.dev/badge/commands/afaizalam2003/master-claude-skill/review.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.00008 | $0.00295 |
| Opus 5 | $0.00004 | $0.00148 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
review 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 7d 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.
This is a copy
100% identical to review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Perform a complete review pass:
- Save work in progress and ensure the working tree is clean except for intentional changes.
- Install tooling (only first run):
pip install --upgrade pip pip install yamllint==1.35.1 check-jsonschema==0.28.4 safety==3.2.4 npm install --global [email protected] - Lint GitHub workflows:
yamllint -d '{extends: default, rules: {line-length: {max: 160}}}' .github/workflows check-jsonschema --schema github-workflow --base-dir . .github/workflows/*.yml - Python syntax check:
python -m compileall marketing-skill product-team c-level-advisor engineering-team ra-qm-team - Markdown sanity check:
markdown-link-check README.md - Optional dependency audit (if
requirements*.txtpresent):for f in $(find . -name "requirements*.txt" 2>/dev/null); do safety check --full-report --file "$f" done - Summarize results in the commit template's Testing section. Fix any failures before continuing.
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.
- 7d ago First seen · 34 lines · 8 tokens per session scan A 8a2a8cf92b8f
review is a command published in the GitHub repository afaizalam2003/Master-claude-skill (2 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 295 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.