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 deliver-changegit 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/deliver-change)<a href="https://agentmods.dev/skills/manusco/resonance/deliver-change"><img src="https://agentmods.dev/badge/skills/manusco/resonance/deliver-change/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/deliver-change"><img src="https://agentmods.dev/badge/skills/manusco/resonance/deliver-change.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.00088 | $0.01112 |
| Opus 5 | $0.00044 | $0.00556 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
resonance-software-deliver-change 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
resonance-software-deliver-change: preserve the software delivery entrypoint
Role: compatibility intake for software delivery. Input: A desired software outcome, bug fix, feature, migration, or release goal. Output: A bounded software request handed to
/goal, or a stopped intake with the scope conflict named. Definition of Done: Software scope is explicit, unrelated work is separated, and the unchanged request plus constraints are delegated exactly once toresonance-ops-goal. This skill does not start or reproduce a goal loop.
This skill preserves an existing software-facing entrypoint. It is not a second
goal loop. resonance-ops-goal owns the contract, approval gate, loop state,
planning, building, verification, evidence, audit, independent review, and ship
proposal. This skill performs software intake and delegates once. It never runs
the downstream delivery pipeline itself.
Prerequisites
- The skill was invoked explicitly or an existing workflow targeted its skill ID.
- The request contains a software delivery outcome, not only a narrow one-step command.
Compatibility flow
- Confirm the entrypoint. If the user did not explicitly invoke this skill and no existing workflow targeted it, route a new end-to-end outcome directly to
/goal. -> verify: this compatibility layer does not compete with Goal during ordinary routing. - Bound software scope. Preserve the user's request, directives, constraints, and provenance. Identify the software outcome. -> verify: no requirement is rewritten or invented.
- Separate unrelated work. Split marketing, sales, finance, leadership, or other independent outcomes and route them to their owners. Do not absorb them into software delivery. -> verify: the Goal handoff contains one coherent software outcome.
- Delegate once. Invoke
resonance-ops-goalwith the unchanged software request and its confirmed constraints. -> verify: exactly one Goal invocation occurs and no downstream delivery specialist is invoked directly by this skill. - Return Goal's result. Preserve Goal's evidence, stop condition, approvals, and ship proposal without adding a second completion claim. -> verify: no nested state, duplicate approval, duplicate audit, or duplicate ship proposal exists.
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.
- 10d ago First seen · 91 lines · 88 tokens per session scan A f2fbf6761dbb
resonance-software-deliver-change is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 5d ago), licensed MIT. It adds 88 tokens to every session and 1,112 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.