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 mracal/vibe-engineering --skill wave-based-remediationgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/wave-based-remediation)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/wave-based-remediation"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/wave-based-remediation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mracal/vibe-engineering/wave-based-remediation"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/wave-based-remediation.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00592 |
| Opus 5 | $0.00017 | $0.00296 |
| Sonnet 5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
vibe-wave-based-remediation 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 10d 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.
This is a copy
100% identical to vibe-wave-based-remediation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-wave-based-remediation
When you have 50 issues, don't fix them randomly. Attack in waves.
When to Use This Skill
- 10+ bugs, issues, or gaps to fix
- After an audit or review that produced many findings
- After
vibe-spec-vs-code-auditreveals many gaps - Technical debt cleanup with many items
When NOT to Use This Skill
- Fewer than 5 issues (just fix them sequentially)
- All issues are the same priority (no need to wave)
- Issues are all in one file (batch-fix is simpler)
Steps
-
Triage all issues into priority:
- P0 — Blocker: Breaks core functionality, security vulnerability, data loss risk
- P1 — High: Wrong behavior, significant UX issue, missing critical feature
- P2 — Medium: Incomplete implementation, minor bugs, documentation gaps
- P3 — Low: Polish, optimization, nice-to-have improvements
-
Group into waves:
- Wave 0: All P0 issues (fix immediately, before anything else)
- Wave 1: All P1 issues, grouped by affected module/file for efficiency
- Wave 2: P2 issues, parallelizable groups
- Wave 3: P3 issues (may defer to backlog)
-
Execute each wave:
- Fix all issues in the wave
- Run tests after the wave
- Verify fixes don't introduce regressions
- Commit the wave as a logical unit
- Do NOT start Wave N+1 until Wave N passes tests
-
Track progress:
Output Format
Wave-Based Remediation
Total Issues: X Waves: Y
| Wave | Priority | Issues | Status |
|---|---|---|---|
| 0 | P0 (Blocker) | 3 | Complete |
| 1 | P1 (High) | 12 | In Progress (8/12) |
| 2 | P2 (Medium) | 25 | Pending |
| 3 | P3 (Low) | 10 | Deferred |
Wave 1 Detail
| Issue | File | Status | Fix |
|---|---|---|---|
| GAP-001 | auth.go | Done | Added token expiry |
Remaining
- Wave 2: 25 issues (ready to start)
- Wave 3: 10 issues (deferred to backlog)
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.
- 10d ago First seen · 69 lines · 34 tokens per session scan A 59b725923ccf
vibe-wave-based-remediation is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 592 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-wave-based-remediation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
code-intelligence-contract
Use when dependency, call-chain, blast-radius, architecture, domain-flow, or unfamiliar-codebase analysis needs an optional vendor-neutral code-intelligence provider.
evidence-first-debugging
Use when debugging a crash, lỗi, failing game, tool, build, service, script, or reproducible local code failure requires repro or reproduction, giả thuyết or ranked hypotheses, instrumentation, root-cause isolation, a minimal fix, regression proof, and a regression test.
bug-hunt-swarm
Use when an unknown crash, intermittent failure, or cross-subsystem bug needs parallel read-only reproduction lanes, ranked hypotheses, suspect paths, and an integrator root-cause plan.
cpp-server-crash-triage
Use when triaging a C++ game server crash, dump, access violation, segmentation fault, stack trace, symbols, or build identity into a stable signature and ranked root-cause plan.
multi-service-local-environment-doctor
Use when diagnosing a multi-service local game environment with port conflicts, process listeners, configured ports, service names, startup dependencies, and cross-project isolation concerns.
unity-asset-guid-meta-audit
Use when auditing Unity asset GUID and meta consistency, duplicate GUIDs, missing meta files, stale references, or import and prefab reference failures without editing assets.