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 skills/himanshu-sangshetti/cursor-stack/retronpx 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.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.00045 | $0.00931 |
| Opus 5 | $0.00023 | $0.00465 |
| Sonnet 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 4d 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.
- 4d 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 (6 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 931 once invoked, about $0.0002 per session on Opus 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
deep-research
Iterative multi-source investigation with contradiction logging—use for audits, vendor comparisons, security posture reviews, benchmarking methodology, literature surveys, ambiguous technical history, regulated domains, unfamiliar APIs, architectural landscape scans, falsifiable claims needing citations, stakeholder…
article-review-tracker
追踪文章审稿意见，将编辑反馈结构化记录并逐条落实。触发词：审稿意见/修改文章/这里写得不好/审稿反馈/帮我追踪这个意见。.
administer-rcss
施测科研人员认知风格量表（RCSS），评估横向整合 vs 垂直深度的认知偏好。当用户选择填写量表、或画像中RCSS数据缺失时使用。.
article-image-angles
分析文章可用的多种配图视角，为每个角度生成提示词草图供用户选择。触发词：帮我分析配图角度/生成多视角草图/配图有几种选择/给我几个配图方案。.
ui-design
Create distinctive, production-grade web interfaces with high design quality using Tailwind CSS. Use for building UI components, pages, dashboards, apps, and web applications. Generates crafted, polished code that avoids generic AI aesthetics.
code-review-codex
Final-gate code review via Codex CLI (codex-5.3, xhigh). Finds bugs, security issues, and regressions before commit. No edits — findings report only.