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 hamzaPixl/pixl-ai --skill retrogit clone --depth 1 https://github.com/hamzaPixl/pixl-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/skills/hamzapixl/pixl-ai/retro)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/retro"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/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/hamzapixl/pixl-ai/retro"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/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.00059 | $0.01613 |
| Opus 5.5 | $0.00024 | $0.00645 |
| Sonnet 5.5 | $0.00012 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00161 |
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Analyzes git history and project data to produce a structured engineering retrospective. Focuses on what shipped, code quality trends, hotspots, and shipping velocity.
Step 1: Determine Time Window
Parse the argument for the time window:
| Argument | Window | git log --since |
|---|---|---|
24h |
Last 24 hours | --since="24 hours ago" |
7d (default) |
Last 7 days | --since="7 days ago" |
14d |
Last 14 days | --since="14 days ago" |
30d |
Last 30 days | --since="30 days ago" |
compare |
Compare current vs previous period | Two git log ranges |
Step 2: Gather Data
Run these commands in parallel:
Commit Analysis
# Commit count and authors
git log --since="7 days ago" --oneline | wc -l
git log --since="7 days ago" --format="%an" | sort | uniq -c | sort -rn
# Commit types (conventional commits — macOS-compatible)
git log --since="7 days ago" --oneline | sed -E 's/^[a-f0-9]+ //' | grep -oE '^(feat|fix|refactor|chore|docs|test|perf|ci|style)' | sort | uniq -c | sort -rn
# Files changed
git log --since="7 days ago" --name-only --format="" | sort | uniq -c | sort -rn | head -20
Code Churn
# Lines added/removed
git log --since="7 days ago" --numstat --format="" | awk '{add+=$1; del+=$2} END {print "+"add, "-"del}'
# Churn by directory
git log --since="7 days ago" --numstat --format="" | awk '{split($3,a,"/"); dir=a[1]"/"a[2]; add[dir]+=$1; del[dir]+=$2} END {for(d in add) print add[d]+del[d], d}' | sort -rn | head -10
Hotspots (High Churn Files)
# Files changed most frequently (potential complexity hotspots)
git log --since="7 days ago" --name-only --format="" | sort | uniq -c | sort -rn | head -10
PR Activity (if GitHub)
# Merged PRs
gh pr list --state merged --search "merged:>=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)" --json number,title,author,mergedAt --limit 50
# Open PRs
gh pr list --state open --json number,title,author,createdAt --limit 20
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 · 161 lines · 59 tokens per session scan A e7dd44b56a9f
retro is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 1,613 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.