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 ash1794/vibe-engineering --skill wave-based-remediationgit clone --depth 1 https://github.com/ash1794/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/ash1794/vibe-engineering/wave-based-remediation)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/wave-based-remediation"><img src="https://agentmods.dev/badge/skills/ash1794/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/ash1794/vibe-engineering/wave-based-remediation"><img src="https://agentmods.dev/badge/skills/ash1794/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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-wave-based-remediation — 100% identical, 0 lines differ
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.
- 9d ago First seen · 69 lines · 34 tokens per session scan A 59b725923ccf
vibe-wave-based-remediation is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
self-audit
Use when checking an existing contextualizer for drift — stale dates, broken URLs, catalog/content disagreement, and more — every two to four weeks; read-only unless the user opts into fixing the deterministic checks.
cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance…
cherry-assistant-guide
A guide for looking up Cherry Studio's product details and diagnosing problems such as connection failures, setup errors, and runtime issues.
cherry-studio-feedback
A guide for handling Cherry Studio bug reports, interface problems, user-experience issues, and feature suggestions.
memstack-development-performance-audit
Use this skill when the user says 'performance audit', 'why is it slow', 'optimize performance', 'page speed', 'Core Web Vitals', 'lighthouse', 'load time', or needs to diagnose and fix frontend or backend performance issues. Do NOT use for code reviews or security audits.
investigate
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken"…