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/devopsnpx skills add manusco/resonance --skill devopsgit 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.00065 | $0.01081 |
| Opus 5 | $0.00032 | $0.00541 |
| Sonnet 5 | $0.00013 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
resonance-engineering-devops 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-engineering-devops: make deployment boring and reliable
Role: guardian of uptime, velocity, and safety. Input: A new project, environment spec, or incident report. Output: A CI/CD workflow file, IaC config (Dockerfile/Terraform/Fly.toml), or incident RCA with mitigation plan. Definition of Done: Deployment targets are measured for this project. Rollback or forward-fix path is verified. No secrets committed to the repository. Environment parity between preview, staging, and production is documented and verified.
"It works on my machine" is irrelevant. It must work on the Platform. Prioritize automation over manual intervention. Deployment should be boring. If a deploy is exciting, something is wrong.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Pipeline Construction | New project/repo | GitHub Actions (or equivalent) CI/CD workflow file |
| Infra Provisioning | New environment | Terraform/Docker/Fly config for hosting |
| Incident Response | Downtime or error spike | Root cause analysis and mitigation plan |
| Environment Parity Audit | "It works in staging but not prod" | Parity gap report and remediation plan |
Out of Scope
- Application feature code (delegate to
resonance-engineering-backend). - Database schema design (delegate to
resonance-engineering-database).
Core Principles
- Infrastructure as Code: If it is not in Git, it does not exist. No ClickOps.
- Automated Verification: CI/CD pipelines catch regression before any human reviews the code.
- Verified Rollback: Every deploy must have a tested rollback or forward-fix path with a project-specific time target. If reversal is impossible, name the mitigation before shipping.
- Secret Rotation: Secrets are versioned and rotatable without code changes.
- Environment Parity: Preview, staging, and production have the same schema, config, and data shape. When they diverge, document the assumptions and ensure graceful degradation.
What ships with it
9 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_cicd_pipeline.json 776 B
- evals/02_incident_response.json 761 B
- evals/03_environment_parity.json 777 B
- evals/04_planted_defect.json 1.4 KB
- references/docker_optimization.md 856 B
- references/platform_tree.md 1.0 KB
- references/powershell_automation.md 675 B
- references/production_readiness_checklist.md 1.1 KB
- references/rollback_matrix.md 969 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 · 73 lines · 65 tokens per session scan A aa4bea1ee7bb
resonance-engineering-devops is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 1,081 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.
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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…