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/o2alexanderfedin/strategic-research-automation-templateWrote 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/o2alexanderfedin/strategic-research-automation-template/discover-opportunities)<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/discover-opportunities"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/discover-opportunities/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/discover-opportunities"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/discover-opportunities.svg" alt="Reviewed on agentmods" width="80" 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.00811 |
| Opus 5 | $0.00004 | $0.00405 |
| Sonnet 5 | $0.00002 | $0.00162 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
discover-opportunities 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 12d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover Opportunities
You are executing the /discover-opportunities command to automatically identify strategic opportunities.
Purpose
Autonomously identify 5-10 strategic opportunity areas by analyzing company capabilities against client domain needs using AI-powered pattern matching and market research.
Steps to Execute
Step 1: Validate Context Files
Check context/company-profile.md exists and has >200 words. Check context/client-info.md exists OR domain documents present. If insufficient context, prompt user to populate files.
Step 2: Identify Domain Documents
Search project root for domain documents (PDFs, markdown files). List discovered documents for context enrichment.
Step 3: Load Company Capabilities
Read context/company-profile.md. Extract:
- Technical expertise areas
- Technology stack and tools
- Industry experience
- Certifications and capabilities
- Team strengths
- Competitive advantages
Step 4: Load Client/Domain Context
Read context/client-info.md and any domain documents. Extract:
- Strategic priorities
- Pain points and challenges
- Industry regulations
- Market trends
- Technology gaps
- Budget and timeline constraints
Step 5: Invoke Opportunity Discovery Skill
Use Task tool to invoke opportunity-discovery skill with context:
- Company capabilities
- Client needs and domain
- All domain documents
- Project configuration
Discovery skill will:
- Analyze capability-need intersections
- Research market opportunities (WebSearch)
- Validate market sizing (WebFetch)
- Identify regulatory tailwinds
- Assess competitive landscape
- Calculate strategic fit scores
- Generate 5-10 opportunity definitions
Step 6: Generate Sprint Definitions
For each discovered opportunity:
- Create sprint number (01-10)
- Generate sprint slug from name
- Write sprint description
- Customize research questions
- Assign priority (High/Medium/Low)
Populate config/sprint-config.yml with all sprints.
Step 7: Create Discovery Report
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.
- 12d ago First seen · 155 lines · 8 tokens per session scan A b19e2b2542ca
discover-opportunities is a command published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 811 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-30.
Other commands, from other repositories
prp-plan
Create comprehensive feature implementation plan with codebase analysis and pattern extraction.
prp-prd
Interactive PRD generator - problem-first, hypothesis-driven product spec with back-and-forth questioning.
sessions
Manage Claude Code session history, aliases, and session metadata.
multi-execute
Multi-model collaborative execution - Get prototype from plan → Claude refactors and implements → Multi-model audit and delivery.
code-review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).
e2e
Legacy slash-entry shim for the e2e-testing skill. Prefer the skill directly.