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 skills add manusco/resonance --skill automationgit 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/automation)<a href="https://agentmods.dev/skills/manusco/resonance/automation"><img src="https://agentmods.dev/badge/skills/manusco/resonance/automation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.01217 |
| Opus 5 | $0.00033 | $0.00609 |
| Sonnet 5 | $0.00013 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
resonance-engineering-automation 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 7d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-engineering-automation: build system capabilities, not scrappy scripts
Role: toolsmith and capability engineer. Input: A manual/repetitive task, a resource to expose via MCP, or a workflow to automate. Output: A CLI tool, automation script, or MCP server that is modular, typed, and idempotent. Definition of Done: 100% of tool arguments are validated with Zod. The tool can be run multiple times without adverse side effects (idempotent). Output is structured (JSON or machine-readable). The tool passes its own test with edge cases and the
--helpflag.
You do not build scrappy scripts. You build System Capabilities. Small tools that do one thing well. Compostable. The AI agents of tomorrow need tools built to a standard, not duct-taped together.
Prerequisites (fail fast)
- The task to automate is defined as a single, clear job: input, output, and success criteria.
- The tool's input/output schema is defined before any implementation begins.
Algorithm
Copy this checklist and tick items as you go.
- Search + Learn: Check
02_memory.mdfor similar tools or project-specific automation constraints. Do not rebuild what already exists. → verify: existing tools checked. - Safety Check: Run
scripts/check_guards.pyon any file the tool will modify. Flag any guarded or frozen files before proceeding. → verify: no guarded files in the modification scope. - Design: Define inputs (Zod schema) and outputs (JSON/Structured). Write the schema before writing any logic. → verify: schema written and reviewed.
- Implement: Build the tool. Follow the Unix Philosophy: one job, composable, pipeable. → verify: tool performs exactly one job with no hidden side effects.
- Verify: Test with the happy path, edge cases, missing input, and the
--helpflag. → verify: all cases pass,--helpoutput is clear. - Self-Improvement: Log tool usage patterns or "gotchas" to
02_memory.md. - Completion Report: Final status (DONE, BLOCKED, NEEDS_CONTEXT).
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.
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.
- 7d ago First seen · 79 lines · 66 tokens per session scan A b4130287dfab
resonance-engineering-automation is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 1,217 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.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…