Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bodangren/git-workflownpx agentmods add skills/bodangren/git-workflow/sprint-managerWrote 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/bodangren/git-workflow/sprint-manager)<a href="https://agentmods.dev/skills/bodangren/git-workflow/sprint-manager"><img src="https://agentmods.dev/badge/skills/bodangren/git-workflow/sprint-manager/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/bodangren/git-workflow/sprint-manager"><img src="https://agentmods.dev/badge/skills/bodangren/git-workflow/sprint-manager.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.01757 |
| Opus 5.5 | $0.00000 | $0.00703 |
| Sonnet 5.5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
sprint-manager 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 2mo 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Manager
Purpose
To autonomously execute a sprint by coordinating the implementation of GitHub issues through a structured workflow that leverages subagents for isolated work and maintains a clean context window for sprint-level coordination.
When to Use
Use this skill in the following situations:
- Starting work on a set of sprint issues from a GitHub milestone
- Implementing multiple issues autonomously with minimal user intervention
- Coordinating a development workflow that requires code review and integration
- Managing serial execution of dependent or independent issues
Prerequisites
- GitHub repository with issues assigned to a milestone
- Git working directory is clean (no uncommitted changes)
ghCLI tool installed and authenticatedgeminiCLI tool installed and authenticated (optional, for plan generation)- Codex MCP available for PR review
- Project has
issue-executorandchange-integratorskills (or equivalent workflow)
Architecture
The sprint manager operates as a coordinator that delegates work to subagents:
Sprint Manager (main context)
│
├── For each issue:
│ ├── 1. Generate implementation plan (Gemini CLI or manual)
│ ├── 2. Create feature branch
│ ├── 3. Launch implementer subagent → creates PR
│ ├── 4. Review PR (Codex MCP)
│ ├── 5. Fix issues if needed (another subagent)
│ ├── 6. Merge on approval
│ └── 7. Launch integrator subagent → cleanup & retrospective
│
└── Report sprint summary
Core Workflow
Phase 1: Sprint Setup
-
Identify sprint issues by querying the GitHub milestone:
gh issue list --milestone "Sprint X" --state open --json number,title,labels -
Prioritize issues based on labels (P0 > P1 > P2) and dependencies
-
Track progress using the TodoWrite tool with all sprint issues
Phase 2: Issue Execution Loop
For each issue in priority order:
Step 1: Generate Implementation Plan
Option A - Use issue-executor skill (if Gemini available):
bash scripts/work-on-issue.sh <issue-number>
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 253 lines · 0 tokens per session scan A e313dae0411f
sprint-manager is a skill published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,757 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.