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/execute-sprint)<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/execute-sprint"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/execute-sprint/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/execute-sprint"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/execute-sprint.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.00011 | $0.01987 |
| Opus 5 | $0.00005 | $0.00993 |
| Sonnet 5 | $0.00002 | $0.00397 |
| Haiku 4.5 | $0.00001 | $0.00199 |
Grade A, and why
execute-sprint 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 11d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Complete Sprint
You are executing the /execute-sprint command to run all 6 tasks for a sprint.
Purpose
Execute all 6 tasks for a sprint with parallel execution of Tasks 01-05, followed by sequential execution of Task 06 (synthesis), ensuring efficient research completion while maintaining quality.
Steps to Execute
Step 1: Validate Sprint
Check $1 is valid sprint number 01-99 Verify sprint directory exists: sprints/$1-/ Verify all 6 task files present Confirm temp directory ready: temp/$1-/ Validate context files populated
Step 2: Load Configuration
Read config/project-config.yml for max_parallel_tasks, git_enabled settings Read config/sprint-config.yml for sprint metadata Read all context files for skill agents
Step 3: Initialize Progress Tracking
Output verbose startup message:
🚀 SPRINT EXECUTION STARTING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Sprint: [sprint-name]
Number: [sprint-number]
Total Tasks: 6
Expected Duration: 30-60 minutes
Configuration:
✓ Sprint directory validated
✓ Context files loaded
✓ Output directory ready: temp/[sprint-number]-*/
✓ Parallel execution enabled (5 tasks simultaneously)
Tasks to Execute:
1. Technical Requirements Research
2. Market & Competitive Analysis
3. Solution Architecture Design
4. Certification Pathway Analysis
5. Implementation Roadmap
6. Final Report Synthesis (after tasks 1-5 complete)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Create progress tracking list with 6 tasks, mark all as pending initially
Step 4: Execute Tasks 01-05 in Parallel
Output progress message:
📊 PHASE 1: PARALLEL RESEARCH (Tasks 01-05)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Launching 5 research agents simultaneously...
🔬 Agent 1: Technical Researcher
→ Analyzing technical requirements, regulations, and SMT feasibility
→ Output: temp/[sprint]/01-technical/
📈 Agent 2: Market Analyst
→ Researching TAM/SAM/SOM, competitors, and customer needs
→ Output: temp/[sprint]/02-market/
🏗️ Agent 3: Solution Architect
→ Designing system architecture and POC specifications
→ Output: temp/[sprint]/03-architecture/
✅ Agent 4: Compliance Analyst
→ Researching certification pathways and testing requirements
→ Output: temp/[sprint]/04-compliance/
🗺️ Agent 5: Roadmap Planner
→ Creating implementation roadmap and partnership strategy
→ Output: temp/[sprint]/05-roadmap/
Expected completion: 20-40 minutes (agents work in parallel)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⏳ Research in progress... (updates will appear as agents complete tasks)
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.
- 11d ago First seen · 274 lines · 11 tokens per session scan A bb9f68bc4f09
execute-sprint is a command published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 1,987 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-30.
Other commands, from other repositories
prp-prd
Interactive PRD generator - problem-first, hypothesis-driven product spec with back-and-forth questioning.
jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
setup-pm
Configure your preferred package manager (npm/pnpm/yarn/bun).
checkpoint
Create or verify a checkpoint in your workflow.
projects
List known projects and their instinct statistics.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.