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/Fomo-Driven-Development/strategic-claude-baseWrote 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/fomo-driven-development/strategic-claude-base/check_plan_for_blockers)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/check_plan_for_blockers"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/check_plan_for_blockers.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.00016 | $0.03713 |
| Opus 5 | $0.00008 | $0.01857 |
| Sonnet 5 | $0.00003 | $0.00743 |
| Haiku 4.5 | $0.00002 | $0.00371 |
Grade A, and why
check_plan_for_blockers 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.
How it starts
The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are tasked with analyzing implementation plans for potential blocking issues by examining the codebase, technical dependencies, related summaries, and research documents.
Plan input provided: $1
Input Format Support
This command supports multiple input formats:
- Single plan:
/check_plan_for_blockers PLAN_0019_16-09-2025-tue_reed-solomon-aligned-strategy.md - Multiple plans:
/check_plan_for_blockers PLAN_0019_16-09-2025-tue_reed-solomon-aligned-strategy.md TEST_0019_16-09-2025-tue_rs-aligned-strategy-testing.md - NNNN number:
/check_plan_for_blockers 0019(finds all plans with that number) - Multiple NNNN:
/check_plan_for_blockers 0019 0020 0021 - With Codex analysis:
/check_plan_for_blockers 0019 --with-codex(adds alternative Codex perspective)
Flag Options
- --with-codex: Enables dual-source analysis using the Codex MCP server for an alternative perspective on blockers and dependencies
Initial Response
When this command is invoked:
-
Check if plan input was provided:
- If plan input provided, proceed with analysis
- If no input provided, respond with:
I'll analyze implementation plans for potential blocking issues by examining the codebase, dependencies, and related work. Please provide plan file(s) or NNNN number(s) to analyze: Examples: - Single plan: `/check_plan_for_blockers PLAN_0019_16-09-2025-tue_reed-solomon-aligned-strategy.md` - Multiple plans: `/check_plan_for_blockers PLAN_0019... TEST_0019...` - NNNN number: `/check_plan_for_blockers 0019` - Multiple NNNN: `/check_plan_for_blockers 0019 0020 0021` - With Codex analysis: `/check_plan_for_blockers 0019 --with-codex` I'll use codebase agents and optionally Codex analysis to identify blockers and propose plan updates.Then wait for the user's input.
Process Steps
Step 1: Plan Discovery and Validation
- Parse input arguments:
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 · 511 lines · 16 tokens per session scan A a57f5366a0b7
check_plan_for_blockers is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 3,713 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-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.