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 rijuvashisht/Magneto --skill retrogit clone --depth 1 https://github.com/rijuvashisht/MagnetoWrote 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/rijuvashisht/magneto/retro)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/retro"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/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/rijuvashisht/magneto/retro"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/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.00000 | $0.00646 |
| Opus 5 | $0.00000 | $0.00323 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 10d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/retro — Sprint Retrospective from Audit Log
Role: Eng Manager
Inputs: audit log + sprint artifacts
Outputs: retro.md
Audit actions: retro.started, retro.drafted
Why This Skill Exists
gstack's /retro is team-aware. Magneto's /retro is data-aware — it reads the hash-chained audit log so retrospectives are grounded in what actually happened, not memory.
The Protocol
Step 1: Choose scope
- Sprint retro:
magneto retro --sprint <id> - Weekly:
magneto retro --week - Project-wide:
magneto retro --project - Global:
magneto retro --global(across all Magneto projects on this machine)
Step 2: Load events
magneto audit tail --sprint <id> # or time-filter
Group events by:
- Skill invocations (how many /think, /plan, /review, /ship)
- Bug findings (from review.findings_recorded payloads)
- Failed fixes (investigate.hypothesis_tested where result: inconclusive)
- Override events (careful.overridden, freeze.blocked_write)
Step 3: Compute metrics
| Metric | Source |
|---|---|
| Sprint cycle time | ship.pr_opened.ts − think.started.ts |
| Bugs caught in review | review.findings_recorded payload |
| Bugs caught in QA | qa.bug_found payload |
| Test coverage delta | ship.tests_bootstrapped + review payloads |
| /careful overrides | careful.overridden count |
Times /freeze blocked a write |
freeze.blocked_write count |
| Plan score vs audit score (boomerang) | scorecard.json |
Step 4: Write retro.md
# Retro: <scope>
**Period:** <range>
**Events:** <count>
## What went well
- <3-5 items from actual events>
## What didn't
- <3-5 items; each must cite an audit event as evidence>
## Metrics
| Metric | Value |
|---|---|
| Cycle time | <hours> |
| Bugs caught early | <count> |
| /careful overrides | <count> |
## Boomerang
<Plan scores from /plan-*-review vs actual audit scores — where did reality diverge from plan?>
## Action items
- <specific, assigned>
## Pattern learnings (to write to memory)
- <pattern + suggested tag>
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.
- 10d ago First seen · 90 lines · 0 tokens per session scan A df6d6c4fcdb7
retro is a skill published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 646 tokens. 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
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
speckit-plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
agent-phase-closeout
A Chinese-language process for closing out a completed work stage and recording its state. It summarizes finished work, preserves decisions, freezes completed interfaces, and writes a resume checkpoint.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.