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/Blakeem/AI-Prompt-Guide-MCPWrote 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/blakeem/ai-prompt-guide-mcp/audit)<a href="https://agentmods.dev/commands/blakeem/ai-prompt-guide-mcp/audit"><img src="https://agentmods.dev/badge/commands/blakeem/ai-prompt-guide-mcp/audit.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.00007 | $0.00058 |
| Opus 5 | $0.00003 | $0.00029 |
| Sonnet 5 | $0.00001 | $0.00012 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
audit 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
Audit
⚠️ REQUIRED WORKFLOW - You MUST follow these instructions:
Load workflow via get_workflow (once per conversation):
get_workflow({ workflow: "audit" })
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 · 13 lines · 7 tokens per session scan A 7f9ca8aa1fa5
audit is a command published in the GitHub repository Blakeem/AI-Prompt-Guide-MCP (4 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 58 once invoked, about $0.0000 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-31.
Other commands, from other repositories
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
ship-ci-review-loop
Command "ship-ci-review-loop" from composio-community/awesome-claude-plugins, covering phase 4: ci & review monitor loop - reference, this phase is mandatory, pr auto-review process, why all comments matter and the monitor loop algorithm.
audit-project
Multi-agent code review with iterative improvement.
sm-scour
Run slop-mop's comprehensive pre-PR sweep for this repository.
pr-review
Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.
code-review
Perform a comprehensive code review of recent changes.