Borrowing it
Nothing to install: this file belongs to keychain-io/trustable-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/keychain-io/trustable-ai/main/.claude/commands/sprint-retrospective.mdgit 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-retrospective)<a href="https://agentmods.dev/commands/keychain-io/trustable-ai/sprint-retrospective"><img src="https://agentmods.dev/badge/commands/keychain-io/trustable-ai/sprint-retrospective/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/commands/keychain-io/trustable-ai/sprint-retrospective"><img src="https://agentmods.dev/badge/commands/keychain-io/trustable-ai/sprint-retrospective.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.01947 |
| Opus 5 | $0.00000 | $0.00974 |
| Sonnet 5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00195 |
Grade A, and why
sprint-retrospective 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 9d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Retrospective Workflow
Project: trusted-ai-development-workbench Workflow: Sprint Retrospective Purpose: Reflect on sprint execution and identify improvements
Output Formatting Requirements
IMPORTANT: Use actual Unicode emojis in reports, NOT GitHub-style shortcodes:
- ✅ Went well | ⚠️ Needs improvement | ❌ Problem
- 🎯 Goal met | 📉 Missed target | 📈 Exceeded
- 👍 Keep doing | 🔄 Change | 🛑 Stop doing
Overview
This workflow facilitates sprint retrospectives by analyzing sprint metrics, gathering team feedback, and creating actionable improvement items.
Prerequisites
- Completed sprint in azure-devops
- Sprint metrics and burndown data
- Team availability for feedback
Initialize Work Tracking
# Initialize work tracking adapter (auto-selects Azure DevOps or file-based)
import sys
sys.path.insert(0, ".claude/skills")
from work_tracking import get_adapter
adapter = get_adapter()
print(f"📋 Work Tracking: {adapter.platform}")
# Set sprint name for retrospective
sprint_name = "Sprint X" # Replace with actual sprint
Workflow Steps
Step 1: Collect Sprint Metrics
- Query sprint work items:
# Get all work items from the sprint sprint_items = adapter.query_sprint_work_items(sprint_name) summary = adapter.get_sprint_summary(sprint_name) print(f"📊 Sprint {sprint_name} Summary:") print(f" Total items: {summary['total_items']}") print(f" Total points: {summary['total_points']}") print(f" Completed points: {summary['completed_points']}") print(f" Completion rate: {(summary['completed_points']/max(summary['total_points'],1))*100:.1f}%") print(f"\n By state: {summary['by_state']}") print(f" By type: {summary['by_type']}") # List completed items completed_states = ['Done', 'Closed', 'Resolved', 'Completed'] completed = [i for i in sprint_items if i.get('state') in completed_states] incomplete = [i for i in sprint_items if i.get('state') not in completed_states] print(f"\n✅ Completed ({len(completed)}):") for item in completed: print(f" WI-{item['id']}: {item['title']}") print(f"\n⏳ Not Completed ({len(incomplete)}):") for item in incomplete: print(f" WI-{item['id']}: {item['title']} [{item['state']}]")
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.
- 9d ago First seen · 272 lines · 0 tokens per session scan A 34bb84e6b026
sprint-retrospective is a command published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,947 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.