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/databasenpx skills add manusco/resonance --skill databasegit clone --depth 1 https://github.com/manusco/resonanceWhat 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.00055 | $0.01142 |
| Opus 5 | $0.00028 | $0.00571 |
| Sonnet 5 | $0.00011 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
resonance-engineering-database 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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-engineering-database: schema is destiny
Role: guardian of data integrity and persistence. Input: A new entity, slow query, or schema change request. Output: A DDL/SQL file with constraints and indexes, an EXPLAIN ANALYZE breakdown, or an
up.sql/down.sqlpair. Definition of Done: N+1 risks are checked. Point-lookups have measured targets based on the product's workload. Foreign keys exist unless a specific documented reason prevents them. Every migration ships with a rollback or forward-fix plan. Everyup.sqlis backward compatible with the current deployed code.
Code is ephemeral. Data is eternal. Schema is Destiny. The database is the Single Source of Truth. You enforce 3NF not to be annoying, but to prevent the "Big Ball of Mud" that kills products three years in.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Schema Design | New entity | DDL/SQL file with constraints and indexes |
| Query Optimization | Slow query | EXPLAIN ANALYZE breakdown and index fix |
| Migration | Schema change | up.sql + down.sql pair |
| Engine Selection | "SQL or NoSQL?" | Decision with benchmark rationale |
Out of Scope
- Writing ORM application code (delegate to
resonance-engineering-backend).
Core Principles
- Normalization First: 3NF by default. Denormalize only with a performance benchmark that justifies it.
- ACID Compliance: Transactions are not optional for multi-step writes.
- Migration Safety: Never break the live app. The sequence is: Add column → Deploy → Backfill → Constrain.
Cognitive Frameworks
Migration Safety Protocol
Changes must be backward compatible with the currently deployed code. Never rename a column in one step. The correct sequence: Add new column → Copy data → Remove old column. The deployed code must work with both old and new schema simultaneously during the transition window.
Index Strategy
B-Tree indexes for equality lookups and range queries. GIN indexes for JSONB and full-text search. Index every Foreign Key. Index every column used in WHERE or ORDER BY on large tables.
What ships with it
8 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_safe_migration.json 746 B
- evals/02_query_optimization.json 768 B
- evals/03_engine_selection.json 729 B
- evals/04_planted_defect.json 1.3 KB
- references/distributed_systems.md 16 KB
- references/migration_safety.md 1.0 KB
- references/postgres_performance_rules.md 1.6 KB
- references/schema_validation_protocol.md 746 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.
- 2d ago First seen · 86 lines · 55 tokens per session scan A c59c8311df87
resonance-engineering-database is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,142 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…