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 agentmods add skills/bodangren/git-workflow/sprint-managernpx skills add bodangren/git-workflow --skill sprint-managergit clone --depth 1 https://github.com/bodangren/git-workflowWhat 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 | $0.00090 | $0.01757 |
| Opus 5 | $0.00045 | $0.00879 |
| Sonnet 5 | $0.00018 | $0.00351 |
| Haiku 4.5 | $0.00009 | $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 3d 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.
- 3d 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 9mo ago), licensed MIT. It adds 90 tokens to every session and 1,757 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…