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/mikeprasad/aria-knowledge/retrospectnpx skills add mikeprasad/aria-knowledge --skill retrospectgit clone --depth 1 https://github.com/mikeprasad/aria-knowledgeWrote 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/mikeprasad/aria-knowledge/retrospect)<a href="https://agentmods.dev/skills/mikeprasad/aria-knowledge/retrospect"><img src="https://agentmods.dev/badge/skills/mikeprasad/aria-knowledge/retrospect.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.1 | $0.00158 | $0.13797 |
| Opus 5 | $0.00079 | $0.06899 |
| Sonnet 5 | $0.00032 | $0.02759 |
| Haiku 4.5 | $0.00016 | $0.01380 |
Grade A, and why
retrospect scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Bundle fetch + grep** — `Bash curl -s <deployed-bundle-url> | grep -F '<unique-marker-string>'`. The unique marker is either a function name from the diff, a comment string the fix added, or a `[<TAG>-DIAG]` instrume The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 667 lines · 158 tokens per session scan A 2378146a2d3c
retrospect is a skill published in the GitHub repository mikeprasad/aria-knowledge (16 stars, last pushed 9d ago), with no licence file. It adds 158 tokens to every session and 13,797 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
github-repo-management
Clone, create, fork repos; manage remotes, releases.
npm-publish
Use when publishing this package to npm — a version release (npm publish), verifying the registry/pi.dev listing, or diagnosing npm auth failures (E403 2FA/token errors). Token-based flow via NPMTOKEN in .env.local with a temp userconfig, the leakage gate before every publish, post-publish verification and…
doc-changelog
CHANGELOG maintenance following Keep a Changelog. Trigger when the user wants to document changes or prepare a release.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.