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-all)<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/execute-all"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/execute-all/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-all"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/execute-all.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.00010 | $0.01687 |
| Opus 5 | $0.00005 | $0.00843 |
| Sonnet 5 | $0.00002 | $0.00337 |
| Haiku 4.5 | $0.00001 | $0.00169 |
Grade A, and why
execute-all 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute All Sprints
You are executing the /execute-all command to run all sprints defined in the project.
Purpose
Execute all sprints in the project with intelligent parallel orchestration, respecting system resources (max_parallel_tasks configuration), followed by cross-sprint comparative analysis.
Steps to Execute
Step 1: Load Configuration
Read config/project-config.yml for:
- max_parallel_tasks (default: 8)
- git_enabled setting
- quality standards
Read config/sprint-config.yml to:
- Count total sprints
- Extract sprint definitions
- Verify all sprint directories exist
Step 2: Validate Setup
Check:
- All sprint directories exist (sprints/XX-*/)
- Context files populated (client-info.md, company-profile.md)
- temp/ and reports/ directories ready
If validation fails, guide user to complete setup.
Step 3: Create Comprehensive Progress Tracking
Calculate total tasks: N sprints × 6 tasks per sprint
Example for 10 sprints:
- Sprint 01: 6 tasks (pending)
- Sprint 02: 6 tasks (pending)
- ...
- Sprint 10: 6 tasks (pending)
- Total: 60 tasks
Initialize all as pending status.
Step 4: Invoke Sprint Executor for Each Sprint
Use Task tool to invoke sprint-executor skill with context: "Execute all sprints defined in config/sprint-config.yml with max parallelism"
Sprint executor manages:
- Parallel sprint launching (up to max_parallel_tasks sprints)
- Wave-based execution (start new sprints as others complete)
- Progress tracking and status updates
- Error handling and recovery
Example execution flow for 10 sprints, max_parallel=8:
Wave 1: Launch sprints 01-08 simultaneously
Wait for any to complete...
Sprint 03 completes → Launch sprint 09
Sprint 01 completes → Launch sprint 10
Continue until all complete
Step 5: Monitor Overall Progress
Track completion across all sprints with VERY DETAILED real-time updates.
Display startup message:
🚀 MULTI-SPRINT EXECUTION STARTING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Sprints: [N]
Total Tasks: [N × 6]
Parallel Execution: Up to [max_parallel_tasks] sprints simultaneously
Expected Duration: 2-4 hours
This will run completely autonomous - you can safely:
• Close this window (progress logged to file)
• Check back periodically for updates
• Monitor log file: tail -f [logfile]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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 · 248 lines · 10 tokens per session scan A f9f088e21a54
execute-all is a command published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 1,687 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-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).
prp-implement
Execute an implementation plan with rigorous validation loops.