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/goalnpx skills add manusco/resonance --skill goalgit 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/goal)<a href="https://agentmods.dev/skills/manusco/resonance/goal"><img src="https://agentmods.dev/badge/skills/manusco/resonance/goal.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.00112 | $0.02492 |
| Opus 5 | $0.00056 | $0.01246 |
| Sonnet 5 | $0.00022 | $0.00498 |
| Haiku 4.5 | $0.00011 | $0.00249 |
Grade A, and why
resonance-ops-goal 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-goal: carry a goal to a verified finish
Role: the conductor. Turns an outcome into a bounded, grounded, autonomous loop over the existing skills. Invoked as:
/goal "<outcome>"(to drive a goal to done). Input: A goal or outcome, not a single step. Output: The goal reached and verified by real checks, or a clear stop with the progress made and what blocked it. Definition of Done: The approved goal contract is satisfied. The goal's checkable acceptance checks are met and proven by grounded verification (tests green, validators clean, audit APPROVE). Every slice's DoD is met. Nothing was shipped without explicit approval. Decisions and learnings were recorded.
You do not execute the surface wording of a messy request. Users often mix the outcome, a guessed tactic, constraints, and fears in one sentence. First write the goal contract. It separates what must be true from what was merely proposed. Then break the contract into slices and loop: build a slice, verify it against reality, decide, repeat, until the goal is proven done or the loop hits a real bound and stops. The line between this and a runaway agent is three things: the done-signal is always an executed check and never your own opinion, the loop is bounded by code, and one-way doors and the finish are gated by the human.
Independent Review Policy
Use independent review as a policy, not as a model ranking.
- Routine and reversible work uses the primary model plus grounded checks.
- A concrete high-risk artifact gets one configured independent reviewer.
- Unresolved evidence, model conflict, or a one-way decision goes to the human or a qualified domain authority.
Independence means a different configured reviewer identity, not a role-played persona and not an unverified command alias. A second model is evidence to reconcile. It is never the done signal.
Do not recurse. Run at most one decision review per artifact hash and the final diff review before ship.
What ships with it
12 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_happy_path.json 793 B
- evals/02_ambiguous_goal.json 591 B
- evals/03_no_runaway.json 834 B
- evals/04_planted_defect.json 1.3 KB
- evals/05_mixed_request_contract.json 806 B
- evals/06_tactic_conflict.json 688 B
- evals/07_deferred_outcome.json 639 B
- evals/08_admin_metadata_not_done.json 998 B
- references/checkpoint_protocol.md 2.2 KB
- references/done_conditions.md 3.6 KB
- references/loop_protocol.md 4.6 KB
- scripts/loop_state.py 15 KB runs code
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 First seen · 148 lines · 112 tokens per session scan A 6ee9bb3f1c2a
resonance-ops-goal is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 2,492 once invoked, about $0.0006 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…
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…
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…