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 commands/hundia/autospec/sprint-closegit clone --depth 1 https://github.com/Hundia/autospecWrote 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/hundia/autospec/sprint-close)<a href="https://agentmods.dev/commands/hundia/autospec/sprint-close"><img src="https://agentmods.dev/badge/commands/hundia/autospec/sprint-close.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00657 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
sprint-close 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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Close
Close a completed sprint and generate summary documentation with docs cross-references.
Usage
/sprint-close [sprint_number]
Example: /sprint-close 4
Instructions
When this command is invoked:
-
Verify sprint is ready to close:
- Read
specs/backlog.md - Check all tickets are ✅ Done or ⏸️ Blocked (with justification)
- If any tickets are still 🔄 or 🧪, warn the user
- Read
-
Gather sprint data:
- Sprint name, goal, and metadata
- All tickets with final status
- Files changed (via
git difforgit log) - Test results from latest test run
- Documentation files created or updated
-
Create sprint summary directory:
- Create
sprints/sprint_X/if it doesn't exist
- Create
-
Generate
sprints/sprint_X/summary.md:
# Sprint X Summary
**Date:** YYYY-MM-DD
**Status:** ✅ COMPLETE
**Theme:** [Sprint theme]
## Overview
[2-3 sentence executive summary]
## Completed Tickets
| # | Ticket | Description | Status | Docs |
|---|--------|-------------|--------|------|
| X.1 | Title | What was done | ✅ | [docs/section/file.md] |
## Documentation Updated
| Doc File | Change | Related Tickets |
|----------|--------|-----------------|
| `docs/api/reference.md` | Added 3 endpoints | X.2, X.3 |
| `docs/architecture/database.md` | Updated ERD | X.1 |
## Key Files Modified
[Table of files changed]
## QA & Test Results
| Suite | Pass | Fail | Total | Notes |
|-------|------|------|-------|-------|
| Unit | X | 0 | X | |
| Integration | X | 0 | X | |
## Retrospective
### What went well
- [Observation]
### What to improve
- [Observation]
- Update viewer data:
- Update
viewer/src/data/backlog.ts— ensure all ticket statuses match final state - Update
viewer/src/data/sprints.ts— add/updateSprintVisualizationwith retrospective data:retrospective.completedAt,keyMetrics,highlights,challengestimelinedata if multi-phase execution occurred
- Build viewer:
cd viewer && npm run build— verify exit 0
- Update
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.
- 5d ago First seen · 95 lines · 0 tokens per session scan A ff61b4fc1cf7
sprint-close is a command published in the GitHub repository Hundia/autospec (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 657 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.