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.
npx agentmods add commands/fomo-driven-development/strategic-claude-base/read_and_execute_plangit 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/read_and_execute_plan)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/read_and_execute_plan"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/read_and_execute_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.00017 | $0.01474 |
| Opus 5 | $0.00009 | $0.00737 |
| Sonnet 5 | $0.00003 | $0.00295 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
read_and_execute_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 5d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Plan
You are tasked with implementing an approved technical plan from .strategic-claude-basic/plan/. These plans contain phases with specific changes and success criteria.
Plan file provided: $1
Optional Pair Programming Navigator (--with-codex)
When the --with-codex flag is present, enable Codex pair-programming mode using the codex-navigator subagent:
Navigator Setup and Context Sharing
-
Launch Navigator: Use the Task tool to start the codex-navigator subagent:
Use Task tool with subagent_type: "codex-navigator" Prompt: "I'm implementing [plan name] and need strategic navigation guidance. Plan Context: - Goal: [primary objective from plan] - Current Phase: [phase being worked on] - Key Constraints: [any critical limitations or requirements] - Files Involved: [main files mentioned in plan] Please provide strategic navigation for this implementation, focusing on architecture, patterns, and quality oversight while I handle the tactical implementation." -
Navigator Availability Handling: If the subagent reports that Codex MCP is unavailable, continue in solo mode:
❌ Codex MCP Navigator unavailable — continuing in solo driver mode. Please configure the Codex MCP server and rerun with `--with-codex` when ready.
Driver-Navigator Collaboration Pattern
-
Structured Communication Cycle:
- Before significant actions: Consult Navigator about approach, risks, and best practices
- During implementation: Update Navigator on progress and any challenges encountered
- After completing sections: Request feedback and guidance for next steps
- At phase boundaries: Confirm completion criteria and validate phase transitions
-
Driver Self-Reflection Protocol:
- After receiving Navigator guidance, restate the approach in your own words
- Evaluate implementation risks and confirm alignment with plan success criteria
- Proactively surface uncertainties or validation needs
- Sanity-check that Navigator's roadmap matches plan phases and checkbox items
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.
- 5d ago First seen · 188 lines · 17 tokens per session scan A 3dec9c72cf2b
read_and_execute_plan is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 17 tokens to every session and 1,474 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.