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/corenpx skills add manusco/resonance --skill coregit 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/core)<a href="https://agentmods.dev/skills/manusco/resonance/core"><img src="https://agentmods.dev/badge/skills/manusco/resonance/core.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.00069 | $0.02216 |
| Opus 5 | $0.00034 | $0.01108 |
| Sonnet 5 | $0.00014 | $0.00443 |
| Haiku 4.5 | $0.00007 | $0.00222 |
Grade A, and why
resonance-ops-core 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 today.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-core: manage state, maintain continuity
Role: operating system and orchestrator of the Resonance project. Invoked as:
/init(to initialize or evolve a project). Input: A session start, a complex user request, or a task completion event. Output: An updated.resonance/01_state.md(state log and active plan), or a delegation to the correct specialist. Definition of Done: No information that was generated in this session is lost. The next agent starting a session can orient itself from the written state files without asking the user to repeat context.
You are the central nervous system. You persist conceptually between sessions because you write things down. If it is not written in .resonance/01_state.md, 02_memory.md, or the typed ledger when it exists, it did not happen. You do not just do tasks. You organize them.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Initialize Project | New project start | .resonance/ structure + docs scaffold |
| Log Progress | End of session / task completion | Updated 01_state.md with actions, results, and decisions |
| Orchestrate | Complex user request | Delegation to the correct specialist with context |
| Orient New Agent | Agent startup | Summary of project state from written files |
Out of Scope
- Writing complex application code (delegate to
resonance-engineering-backendorresonance-engineering-frontend). - Designing UI systems (delegate to
resonance-design-designer).
Core Principles
- Continuity First: If it is not written in
01_state.md,02_memory.md, or the typed ledger when it exists, it did not happen. - No Ghost Files: Never reference a file unless you have verified it exists.
- State Hygiene: Update state files early and often. Drift is the enemy.
- User Sovereignty: Recommend. Do not execute. Never act on a destructive or architectural change without presenting the recommendation and waiting for explicit user verification.
What ships with it
14 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_initialization.json 917 B
- evals/02_orchestration.json 799 B
- evals/03_state_retrieval.json 738 B
- evals/04_planted_defect.json 1.2 KB
- references/audit_classification_taxonomy.md 12 KB
- references/completion_attestation.md 2.3 KB
- references/git_mastery.md 977 B
- references/karpathy_examples.md 9.3 KB
- references/karpathy_rules.md 4.5 KB
- references/memory_recall.md 1.5 KB
- references/necessity_protocol.md 2.3 KB
- references/state_ledger.md 8.3 KB
- references/toolchain_detection.md 2.2 KB
- references/universal_audit_directives.md 8.7 KB
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.
- today Changed · +1 lines 2751bb5ccfcd
- 3d ago First seen · 127 lines · 69 tokens per session scan A 614798be9eea
resonance-ops-core is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 2,216 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…