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/update-roadmapnpx skills add manusco/resonance --skill update-roadmapgit 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/update-roadmap)<a href="https://agentmods.dev/skills/manusco/resonance/update-roadmap"><img src="https://agentmods.dev/badge/skills/manusco/resonance/update-roadmap.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.00055 | $0.00683 |
| Opus 5 | $0.00028 | $0.00342 |
| Sonnet 5 | $0.00011 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
resonance-ops-update-roadmap 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-update-roadmap: map must match territory
Role: the Synchronizer and GPS. Invoked as:
/update-roadmap(to sync state.md with git log). Input:git logand.resonance/01_state.md. Output: Updated.resonance/01_state.md. Definition of Done:01_state.mdaccurately reflects the last 10 git commits. Completed tasks are marked done. The immediate next step is recalculated.
The Plan says we are at Step 1. The Code says we are at Step 5. Drift is failure. You must make the Map match the Territory.
Prerequisites (fail fast)
-
.resonance/01_state.mdexists. - Git history exists.
Algorithm (Execution)
Copy this checklist and tick items as you go.
- Read Territory: Run
git log -n 10 --onelineto identify what actually happened. - Read Map: Read
.resonance/01_state.mdto identify what we thought happened. - Reconcile:
- Mark Done: If Git says the feature is merged, mark it
[x]in the state. - Context Update: Add any new constraints found in the commit messages.
- Next Step: Re-calculate the immediate next step.
- Mark Done: If Git says the feature is merged, mark it
- Governance: Save the updated
01_state.md.
Recovery
- Conflict → If Map and Territory diverge wildly, favor the Territory (Git). Update the Map to reflect Reality. Never revert code just to match an old plan.
Out of Scope
- Planning new features (delegate to
/plan).
Cognitive Frameworks
The Reality Check
Most plans fail because the map becomes outdated. Code is the only objective truth. When in doubt, read the code.
Reference Library
- Karpathy Rules: Universal coding standards (Simplicity, Surgical).
Operating Standard
Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory; when .resonance/ledger/ exists it is the system of record for decisions, lessons, metrics, customers, and experiments, while 02_memory.md keeps [lib] notes and pointers).
What ships with it
4 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 · 56 lines · 55 tokens per session scan A 8c0f7f8ae139
resonance-ops-update-roadmap is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 683 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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…