
If you're running Claude Code sessions throughout a sprint and want to see what you actually accomplished, this pulls everything from your local Agent Monitor API and formats it into a proper retrospective document. You get sessions grouped by project directory, cost breakdowns per model, token efficiency stats like cache hit rates, and velocity metrics you can compare sprint over sprint. The retrospective section is genuinely useful because it surfaces your most expensive sessions and highest error rates alongside what worked well. It's basically turning your localhost:4820 monitoring data into something you could actually show a team lead without having to manually spreadsheet it all together.
$ npx -y skills add hoangsonww/claude-code-agent-monitor --skill sprint-summary --agent claude-codeInstalls into .claude/skills of the current project.
Generate a sprint summary from Claude Code Agent Monitor data.
The user provides: $ARGUMENTS
This may be:
Fetch sprint data from http://localhost:4820:
GET /api/sessions?limit=500 — all sessions in range (default sort: most recently updated first)GET /api/analytics — aggregated metricsGET /api/pricing/cost — total costsGET /api/events?session_id={id} — event detailsCompile sprint summary:
Group sessions by working directory (project):
/path/to/project)
/path/to/other)
| Metric | Sprint | Previous Sprint | Trend |
|---|---|---|---|
| Sessions/day | N | N | ↑/↓ |
| Avg session duration | Nm | Nm | ↑/↓ |
| Cost/session | $N | $N | ↑/↓ |
| Tokens/session | N | N | ↑/↓ |
| Completion rate | N% | N% | ↑/↓ |
Professional sprint report suitable for sharing with team leads or managers:
Sponsors