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/keychain-io/trustable-ai/sprint-completiongit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/keychain-io/trustable-ai/sprint-completion)<a href="https://agentmods.dev/commands/keychain-io/trustable-ai/sprint-completion"><img src="https://agentmods.dev/badge/commands/keychain-io/trustable-ai/sprint-completion.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.02261 |
| Opus 5 | $0.00000 | $0.01130 |
| Sonnet 5 | $0.00000 | $0.00452 |
| Haiku 4.5 | $0.00000 | $0.00226 |
Grade A, and why
sprint-completion 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Completion Workflow
Project: trusted-ai-development-workbench Workflow: Sprint Completion Purpose: Close sprint, archive data, calculate metrics, and prepare for next sprint
Output Formatting Requirements
IMPORTANT: Use actual Unicode emojis in reports, NOT GitHub-style shortcodes.
Workflow Overview
┌─────────────────────────────────────────────────────────────────────────────┐
│ SPRINT COMPLETION │
│ │
│ Step 1: Collect final sprint metrics │
│ Step 2: /scrum-master → Analyze incomplete work (if any) │
│ Step 3: Process incomplete items (carry over / backlog) │
│ Step 4: Calculate performance metrics │
│ Step 5: Generate completion report │
│ Step 6: Archive sprint data │
│ Step 7: Prepare next sprint │
│ │
│ Agent command spawns a FRESH CONTEXT WINDOW via Task tool │
└─────────────────────────────────────────────────────────────────────────────┘
Initialize Workflow
current_sprint = input("Sprint to close (e.g., Sprint 1): ")
next_sprint = input("Next sprint name (e.g., Sprint 2): ")
# Load all sprint work items
from pathlib import Path
import yaml
sprint_items = []
work_items_dir = Path(".claude/work-items")
for f in work_items_dir.glob("*.yaml"):
with open(f) as file:
item = yaml.safe_load(file)
if item.get('sprint') == current_sprint:
sprint_items.append(item)
print(f"📋 Found {len(sprint_items)} items in {current_sprint}")
Step 1: Collect Final Sprint Metrics
# Categorize items
completed_states = ['Done', 'Closed', 'Resolved', 'Completed']
completed = [i for i in sprint_items if i['status'] in completed_states]
incomplete = [i for i in sprint_items if i['status'] not in completed_states]
# Calculate metrics
total_points = sum(i.get('story_points', 0) for i in sprint_items)
completed_points = sum(i.get('story_points', 0) for i in completed)
completion_rate = (completed_points / total_points * 100) if total_points > 0 else 0
print(f"📊 Final Sprint Metrics:")
print(f" Total: {len(sprint_items)} items ({total_points} pts)")
print(f" ✅ Completed: {len(completed)} ({completed_points} pts)")
print(f" ⏳ Incomplete: {len(incomplete)}")
print(f" 📈 Completion Rate: {completion_rate:.1f}%")
print(f" 🚀 Velocity: {completed_points} story points")
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 · 371 lines · 0 tokens per session scan A 2a2b489954ef
sprint-completion is a command published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,261 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.