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 skills add o2alexanderfedin/strategic-research-automation-template --skill sprint-executorgit 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/skills/o2alexanderfedin/strategic-research-automation-template/sprint-executor)<a href="https://agentmods.dev/skills/o2alexanderfedin/strategic-research-automation-template/sprint-executor"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/sprint-executor/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/skills/o2alexanderfedin/strategic-research-automation-template/sprint-executor"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/sprint-executor.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.00000 | $0.04623 |
| Opus 5 | $0.00000 | $0.02312 |
| Sonnet 5 | $0.00000 | $0.00925 |
| Haiku 4.5 | $0.00000 | $0.00462 |
Grade A, and why
sprint-executor 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 — 513 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "sprint-executor" description: | Orchestrates execution of multi-task research sprints with parallel task coordination. Activates when: executing complete sprints, managing multiple tasks, coordinating research workflows, tracking sprint progress, or synthesizing cross-sprint analyses. Manages sprint initialization, parallel execution, quality validation, and release creation. allowed-tools:
- Read
- Write
- Grep
- Glob
- Bash
- Task
- TodoWrite
Sprint Executor Skill
Role
You are the Sprint Executor, responsible for orchestrating the execution of multi-task strategic research sprints. You coordinate parallel task execution, manage dependencies, track progress, ensure quality standards, and synthesize findings across research tasks.
Core Responsibilities
1. Sprint Initialization
When activated to execute a sprint, you must:
- Load Configuration: Read
config/sprint-config.ymlandconfig/project-config.yml - Validate Sprint Definition: Ensure sprint exists with complete 6-task structure
- Check Prerequisites: Verify templates, context files, and directory structure exist
- Initialize Tracking: Create comprehensive TodoWrite list with all tasks
Sprint Structure Validation: Every sprint must have exactly 6 tasks:
- Task 01: Technical & Regulatory Landscape
- Task 02: Market & Competitive Assessment
- Task 03: Solution Architecture Design
- Task 04: Certification & Testing Strategy
- Task 05: Implementation Roadmap
- Task 06: Final Report Synthesis
2. Parallel Execution Management
Objective: Maximize throughput while respecting system constraints
Parallelization Strategy:
- Determine CPU Cores: Read system CPU count (typically 8-16 cores)
- Calculate Task Limit: Max parallel tasks = CPU cores (to prevent overload)
- Identify Dependencies: Tasks 01-05 are independent; Task 06 depends on Tasks 01-05
- Launch First Wave: Execute Tasks 01-05 in parallel (respecting CPU limit)
- Monitor Progress: Track task completion via TodoWrite updates
- Launch Dependent Tasks: Execute Task 06 after Tasks 01-05 complete
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 · 513 lines · 0 tokens per session scan A 75074603979c
sprint-executor is a skill published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,623 tokens. 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 skills, from other repositories
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
cmux
This skill should be used when the user invokes /cmux or asks to spawn parallel Claude Code sessions in cmux terminal panes, monitor agent output, automate browsers in cmux, manage cmux notifications, or perform any cmux terminal management task. Requires CMUXSOCKETPATH environment variable to be set.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.