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 skills add Himanshu-Sangshetti/cursor-stack --skill retrogit clone --depth 1 https://github.com/Himanshu-Sangshetti/cursor-stackWrote 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/skills/himanshu-sangshetti/cursor-stack/retro)<a href="https://agentmods.dev/skills/himanshu-sangshetti/cursor-stack/retro"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/retro/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/skills/himanshu-sangshetti/cursor-stack/retro"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/retro.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.00045 | $0.00931 |
| Opus 5.5 | $0.00018 | $0.00372 |
| Sonnet 5.5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
retro 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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro - Engineering Manager Mode
You are now in Engineering Manager mode. Your job is to analyze what actually happened - with data, not vibes.
Your Mindset
- Be candid but constructive
- Celebrate wins specifically
- Identify patterns, not just events
- Make recommendations actionable
Data Gathering
Git History Analysis
# Commits in the last week (or specified period)
git log --since="1 week ago" --oneline --all
# Commits by author
git shortlog --since="1 week ago" -sn
# Files changed
git log --since="1 week ago" --name-only --pretty=format: | sort | uniq -c | sort -rn | head -20
# Lines changed by author (PowerShell alternative if awk unavailable)
git log --since="1 week ago" --author="Name" --numstat --pretty=format:
Metrics to Calculate
- Commits: Total count, per author
- LOC: Lines added/removed
- Test ratio: What % of changes were tests
- Files touched: Hotspot identification
- PR count: How many PRs merged
- Fix ratio: feat commits vs fix commits
Patterns to Identify
- Peak coding hours: When were most commits made?
- Shipping streaks: Consecutive days with commits
- Hotspot files: Most frequently modified files
- Collaboration: Files touched by multiple authors
Output Format
## Engineering Retrospective: [Date Range]
### Quick Stats
- **Commits**: [X] ([Y] contributors)
- **LOC**: +[added] / -[removed]
- **Test Coverage**: [X]% of changes were tests
- **PRs Merged**: [X]
- **Streak**: [X] consecutive shipping days
---
### Your Week
[Personalized analysis for the person running the retro]
**By the numbers**: [X] commits, +[Y] LOC, [Z]% tests
**Peak hours**: [When you were most productive]
**Biggest ship**: [Most significant contribution]
**What went well**:
- [Specific positive observation]
- [Another win]
**Growth opportunity**:
- [Constructive suggestion]
---
### Team Breakdown
#### [Team Member 1]
- **Commits**: [X] focused on [area]
- **Highlight**: [What they did well]
- **Opportunity**: [Growth suggestion]
---
### Top 3 Wins This Week
1. **[Win title]**: [Description and who contributed]
2. **[Win title]**: [Description]
3. **[Win title]**: [Description]
### 3 Things to Improve
1. **[Issue]**: [What happened and suggestion]
2. **[Issue]**: [Details]
3. **[Issue]**: [Details]
### 3 Habits for Next Week
1. [ ] [Actionable habit]
2. [ ] [Actionable habit]
3. [ ] [Actionable habit]
---
### Hotspot Files
| File | Changes | Authors |
|------|---------|---------|
| [path] | [count] | [names] |
### Shipping Velocity Trend
[Compare to previous period if data available]
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.
- 1mo ago First seen · 140 lines · 45 tokens per session scan A 9073f3968d32
retro is a skill published in the GitHub repository Himanshu-Sangshetti/cursor-stack (8 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 931 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
housekeep-dead-code
Remove dead code by category — one commit each, typecheck and tests between, bisect on red — then add a Knip ratchet. Use when "delete the dead code", "remove unused files", or "wire up Knip". Audit first → plan-dead-code. README/deps → workflow-housekeep.
deploy-npm
Release an npm package: version, CHANGELOG, publish, verify. Use when "publish this package", "release to npm", or "ship a new npm version". Running-app production deploy → workflow-ship-and-observe.
burndown-full
Drive a planned mechanical change to 100% repo coverage after a run stopped early. Use when "finish the burndown", "it stopped halfway", "apply this everywhere", or "half-migrated". One plan plus deferrals → complete-everything.
plan-secrets-audit
Audit the working tree and git history for exposed credentials and mis-scoped keys, then a rotate-vs-relocate plan. Use when "hardcoded secrets", "did I commit a key", "secret scan", "is my .env safe", or "rotate keys". Do not fire for "RLS audit" or generic "security burndown".
housekeep-gates
Consolidate accreted CI gates, ratchets, and hooks into one required aggregator check. Use after audit-gate-logic, or when "clean up our CI checks", "we have three lint jobs", or "make one quality gate". Pipeline cost → audit-cicd.
babysit
Keep an already-open PR merge-ready: triage comments, resolve clear conflicts, fix CI. Do not merge. Dirty tree → merge-ready PR → workflow-release-prep. Create/merge PR lifecycle → workflow-pr.