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/handovernpx skills add manusco/resonance --skill handovergit 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/handover)<a href="https://agentmods.dev/skills/manusco/resonance/handover"><img src="https://agentmods.dev/badge/skills/manusco/resonance/handover.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.00090 | $0.01018 |
| Opus 5 | $0.00045 | $0.00509 |
| Sonnet 5 | $0.00018 | $0.00204 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
resonance-ops-handover 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.
/handover: capture the session for the next person
Role: session scribe and context preservationist. Input: Current conversation context + git log +
.resonance/state files +task.md. Output:docs/handovers/YYMMDD_handover.mdwritten or appended..resonance/01_state.md"Next Session" updated. Definition of Done: A colleague with zero prior context can read the handover and know what was built, what was decided, what needs doing next, and where the risks are.
The conversation history is the richest source. Run this before the session ends.
Source Priority
Mine these in order:
- Current session context: the conversation history. What was discussed, built, decided, and blocked. Use it first; it contains what no file captures.
git log --oneline -20: concrete evidence of what landed. Run as a shell command..resonance/01_state.md: current phase, goal, blockers.task.md: checked items (done) vs. unchecked (open)..resonance/02_memory.md: decisions and lessons from prior sessions.
If a source is missing, skip it silently. Do not fabricate.
Same-Day Logic
- Compute today's date in
YYMMDDformat. - Check if
docs/handovers/<YYMMDD>_handover.mdexists via search. - File does not exist: create it using the full template from handover_structure.md.
- File exists: append only. Add a
---divider followed by### Session <HH:MM>as a heading, then write the same 7 sections scoped to this session's delta. Do not re-copy the earlier content.
Operational Sequence
- Read
.resonance/01_state.md(if it exists). - Read
task.md(if it exists). - Run
git log --oneline -20as a shell command. - Note today's date (
YYMMDD) from system or the git log timestamps. - Check whether
docs/handovers/<YYMMDD>_handover.mdalready exists. - Synthesize from all sources. The session context leads; files confirm and fill gaps.
- Write (new file) or append (existing file, with divider + timestamp heading).
- Update
.resonance/01_state.md"Next Session" to reference the handover path and the top open TODO.
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 · 90 tokens per session scan A 34d7f87db0ae
resonance-ops-handover is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,018 once invoked, about $0.0005 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…