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 manusco/resonance --skill update-resonancegit 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-resonance)<a href="https://agentmods.dev/skills/manusco/resonance/update-resonance"><img src="https://agentmods.dev/badge/skills/manusco/resonance/update-resonance/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/manusco/resonance/update-resonance"><img src="https://agentmods.dev/badge/skills/manusco/resonance/update-resonance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.02626 |
| Opus 5 | $0.00026 | $0.01313 |
| Sonnet 5 | $0.00010 | $0.00525 |
| Haiku 4.5 | $0.00005 | $0.00263 |
Grade A, and why
resonance-ops-update-resonance 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-update-resonance: upgrade the framework, preserve the project
Role: the Maintainer. Invoked as:
/update-resonance. Input: target project, desired Resonance version or source checkout. Output: upgraded Resonance framework files, verified against the target project. Definition of Done: managed framework files are upgraded, project memory and application code are untouched, backups exist, validation passes, and the operator can see exactly what changed.
You are upgrading a public framework inside a real project. Treat the project as the source of truth. Do not force a bulk replacement over a dirty or customized workspace.
Prerequisites (fail fast)
- Source version is resolved with the Source Resolution order below.
- Target project root is confirmed.
- Git status has been classified by path.
- No unresolved conflicts exist in any path the upgrade would touch.
- A backup location outside the managed replacement paths is ready.
- The installation profile is known:
sourceorcompiled. A legacy target with generated skills but no profile is blocked until the owner chooses.
Source Resolution
A target project does not need to record the Resonance upstream URL. Most upgraded projects will only have .agents/ and local memory. Resolve the source in this order:
- Explicit source from the user: local path, Git URL, branch, tag, or commit.
- Local trusted checkout: a user-provided or configured Resonance source path, if it exists and its version matches the requested upgrade.
- Installed package metadata: if the target contains a framework manifest with repository and version fields, use it as a hint, then verify it against the fetched source.
- Official public source: fetch
https://github.com/manusco/resonance.gitwithgh repo clone manusco/resonanceorgit clone https://github.com/manusco/resonance.gitinto a temp directory outside the target project. - Blocked: if no source can be fetched or read, stop before edits and report the exact command or path needed.
What ships with it
9 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.
- evals/01_case.json 903 B
- evals/02_case.json 905 B
- evals/03_case.json 384 B
- evals/04_memory_migration.json 1004 B
- evals/05_planted_defect.json 1.0 KB
- evals/06_conflict_in_managed_path.json 805 B
- evals/07_project_agents_preserved.json 856 B
- evals/08_source_resolution_no_upstream.json 968 B
- evals/09_notice_cannot_apply.json 930 B
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.
- 6d ago Changed · +7 lines 99c10bd4bfe1
- 9d ago First seen · 129 lines · 51 tokens per session scan A 7dcca1f957bd
resonance-ops-update-resonance is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 2,626 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…
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…
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…