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/manusco/resonance/retronpx skills add manusco/resonance --skill retrogit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/retro)<a href="https://agentmods.dev/skills/manusco/resonance/retro"><img src="https://agentmods.dev/badge/skills/manusco/resonance/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.1 | $0.00058 | $0.00901 |
| Opus 5 | $0.00029 | $0.00451 |
| Sonnet 5 | $0.00012 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
resonance-ops-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 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.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-retro: data-driven retrospectives
Role: the Analytics Officer. Invoked as:
/retro(to analyze git history and generate a retro). Input: Timeframe (e.g., "last 7 days"). Output: A highly structured Retro Report indocs/retros/. Definition of Done: Retro report generated based on objective git data, including Focus Score, Complexity Delta, and Test Ratio. Narrative balances mathematical truths with human empathy.
Most retros are feeling-based. This protocol is data-based. Look at git history to discover what was actually accomplished, who drove it, and where the hidden drag was.
Prerequisites (fail fast)
- Must be run inside a valid git repository.
- Clean working tree.
Algorithm (Execution)
Copy this checklist and tick items as you go.
- Data Gathering (The Git Sweep): Run
git log --since="X days ago" --oneline --stat. Group commits by author. Identify code churn vs adding new capability. Determine Test Ratio (Lines of tests vs Lines of application code). - Metric Computation: Calculate the Retro Metrics using the exact definitions and git commands in Retro Metrics (compute them the same way every time, not by eye):
- Shipping Streak: Consecutive calendar days with at least one commit.
- Focus Score: Share of commits that stayed inside one top-level area vs commits that sprayed across three or more.
- Complexity Delta: Net lines (insertions minus deletions), read against what actually shipped.
- Test Ratio: Lines of test code changed vs application code changed.
- Narrative Assembly: Draft the retrospective document:
- The Big Picture: 3-sentence summary of the week's theme.
- Objective Metrics: Commits, LOC Changed, Active Days.
- Highlights & Praise: Give credit where credit is due.
- Growth Opportunities: Where did we stumble?
- The Core Question: "Are we moving faster this week than last week?"
- Governance: Write
retro_YYYY_MM_DD.mdindocs/retros/. Ask the user what action items they want to extract from this retro into the planning queue.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 63 lines · 58 tokens per session scan A 2552a90ad996
resonance-ops-retro is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 901 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…