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/research_phasegit 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/research_phase)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/research_phase"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/research_phase.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.00009 | $0.03382 |
| Opus 5 | $0.00005 | $0.01691 |
| Sonnet 5 | $0.00002 | $0.00676 |
| Haiku 4.5 | $0.00001 | $0.00338 |
Grade A, and why
research_phase 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 — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are tasked with conducting focused research on a specific phase from the product roadmap. You should validate product documentation exists, extract phase-specific requirements, and conduct comprehensive research aligned with the phase objectives and deliverables.
Phase number provided: $1
Initial Response
When this command is invoked:
-
Check if phase number was provided:
- If a phase number was provided as parameter (e.g., "2.3", "1", "Phase 2.1"), proceed with validation
- If no phase number provided, respond with:
I'll help you research a specific phase from your product roadmap.
Please provide:
1. The phase number you want to research (e.g., "1", "1.2", "2.3")
2. Optional focus area or specific aspect to emphasize
Example: `/research_phase 2.3` or `/research_phase 1.1 architecture`
I'll validate your product documentation, extract phase details, and conduct focused research on that phase.
Then wait for the user's input.
Process Steps
Step 1: Product Documentation Validation
-
Check for required product documentation files:
- Look for existence of these files in
.strategic-claude-basic/product/:PRD.md(Product Requirements Document) - REQUIREDARCHITECTURE.md(System Architecture) - REQUIREDROADMAP.md(Product Roadmap) - REQUIREDREFERENCES.md(Local Repository References) - OPTIONAL
- Look for existence of these files in
-
If any required files are missing:
Product documentation validation failed. Missing required files: - [ ] PRD.md - Product Requirements Document - [ ] ARCHITECTURE.md - System Architecture - [ ] ROADMAP.md - Product Roadmap To use phase-based research, you need complete product documentation. Please first create your product documentation using: `/create_product_roadmap [research_file1].md [research_file2].md` This will generate all required product documentation files based on your research.Stop here and wait for user to create missing documentation.
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 · 432 lines · 9 tokens per session scan A 2f3e72130e7d
research_phase is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 3,382 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.