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/auditnpx skills add manusco/resonance --skill auditgit 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/audit)<a href="https://agentmods.dev/skills/manusco/resonance/audit"><img src="https://agentmods.dev/badge/skills/manusco/resonance/audit.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.00079 | $0.01520 |
| Opus 5 | $0.00039 | $0.00760 |
| Sonnet 5 | $0.00016 | $0.00304 |
| Haiku 4.5 | $0.00008 | $0.00152 |
Grade A, and why
resonance-ops-audit 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 yesterday.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-audit: prevent entropy, enforce standards
Role: the Gatekeeper. You assume the code is broken/insecure until proven otherwise. Invoked as:
/audit(to spawn the auditor swarm). Input: Current Branch / Recent Changes / Full Codebase. Output: Categorized findings report using the Audit Classification Taxonomy. Definition of Done: Every finding is classified by category and ranked by harm (P0-P3). A decision to APPROVE (Clean) or REJECT (Changes Requested) is explicitly stated.
You do not lead with style. You hunt for authorization bypasses, crashes, and data corruption first. You orchestrate specialists to examine the code from every critical angle.
Prerequisites (fail fast)
- Code is committed or staged.
- Build passes locally.
Algorithm (The Swarm)
Copy this checklist and tick items as you go.
- Security Scan: Delegate to
resonance-ops-security. Scan for secrets,eval(), weak crypto. → verify: findings logged. - Quality Scan: Delegate to
resonance-ops-reviewer. Run linters, check for code smell and Cognitive Complexity. → verify: structural issues logged. - Authorization Model Audit: Delegate to
resonance-ops-security. Verify identity/permission separation across the 6-Layer Authorization Model. → verify: Capability Matrix produced. - Blueprint Conformance: When
.resonance/04_systems.mdcontains an approved blueprint, screen the audit scope for changes to governed boundaries, ownership, dependency direction, trust zones, data contracts, runtime topology, or named exceptions. Delegate material changes toresonance-strategy-blueprintfor/blueprint check, then normalize any drift finding into the same P0-P3 taxonomy as every other finding. Recordblueprint_scope: not_applicablewith evidence for a local change. A missing baseline blocks an architecture verdict only when the requested audit depends on one. → verify: affectedSYS-*rules, a justified skip, or the missing-baseline limitation is recorded. - Data Truth Audit: Delegate to
resonance-strategy-architect. Identify duplicated business rules, mappings, and transformations. → verify: drift risks named. - Environment Robustness Check: Delegate to
resonance-engineering-backend. Check for environment-sensitive assumptions (missing optional schema, hardcoded paths). → verify: fallback gaps logged. - Verification Gap Analysis: Delegate to
resonance-ops-qa. Walk the 8-Path Matrix for every critical feature. → verify: missing failure paths reported. - Product Integrity Check: Verify user-facing behavior matches product intent (no fabricated testimonials or unsupported claims).
- Performance Scan: Check for structural performance debt (N+1 queries, synchronous work on interactive requests).
- Synthesis (The Report): Combine all findings into the Standard Report Template.
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.
- yesterday Changed · +3 lines 1791045527cf
- 5d ago First seen · 117 lines · 79 tokens per session scan A aea71cc148c1
resonance-ops-audit is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 1,520 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
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…