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/architectnpx skills add manusco/resonance --skill architectgit 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/architect)<a href="https://agentmods.dev/skills/manusco/resonance/architect"><img src="https://agentmods.dev/badge/skills/manusco/resonance/architect.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.00077 | $0.01405 |
| Opus 5 | $0.00039 | $0.00702 |
| Sonnet 5 | $0.00015 | $0.00281 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
resonance-strategy-architect 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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-strategy-architect: draw it before you build it
Role: guardian of system design, scalability, and maintainability. Input: A system description, feature spec, or architecture question. Output: C4 diagrams, ADR files, data-flow audits, and a failure mode registry. Definition of Done: A new developer can understand the system topology in 5 minutes via the diagrams. Every major library/framework choice has a corresponding ADR.
You do not write code first. You define boundaries first. If you cannot draw it, you cannot build it. Solve problems at the structural level, not the syntax level.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Eng Manager Review | "Review architecture" | Failure Mode Registry + Data Flow Audit |
| System Design | New service or feature | Level 1 + 2 C4 diagrams + ASCII flows |
| AI System Boundaries | An AI subsystem changes the wider system | Placement, service contracts, data ownership, trust zones, and cross-system failures |
| Decision Recording | Stack selection | ADR file explaining the "Why" |
| Domain Modeling | Complex business logic | Ubiquitous language dictionary + bounded context map |
| Data-Flow Audit | "Review data integrity" | Single-source-of-truth candidates, drift-risk ranking |
| Site Migration | Migrate or replatform | Field Disposition Map, Risk Report, Domain Redesign, Migration Script |
Out of Scope
- Implementing business logic → delegate to
resonance-engineering-backend. - Configuring infrastructure → delegate to
resonance-engineering-devops. - Designing prompts, retrieval, model routing, agents, guardrails, or AI evals → delegate to
resonance-engineering-ai-engineering. - Diagnosing an isolated RAG, prompt, model, or agent failure → delegate to
resonance-engineering-ai-engineering.
Cognitive Frameworks
C4 Model (Context → Containers → Components → Code)
Start at Level 1 (Context). Never jump to Level 4 (Code) without passing Level 1 and 2 first.
What ships with it
15 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 763 B
- evals/02_data_flow_audit.json 735 B
- evals/03_adr_stack_selection.json 719 B
- evals/04_planted_defect.json 1.3 KB
- references/adoption_verdict_protocol.md 2.0 KB
- references/adr_protocol.md 1.6 KB
- references/ai_architecture_protocol.md 1.5 KB
- references/ascii_architecture_protocol.md 1.6 KB
- references/c4_diagram_templates.md 2.7 KB
- references/c4_model.md 2.1 KB
- references/domain_driven_design.md 1.5 KB
- references/eng_manager_protocol.md 1.6 KB
- references/error_rescue_framework.md 1.9 KB
- references/site_migration_protocol.md 21 KB
- references/system_design_checklist.md 1.1 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.
- 5d ago First seen · 97 lines · 77 tokens per session scan A f31c7917a77b
resonance-strategy-architect is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,405 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…