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 vibe-flake-root-causegit 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/vibe-flake-root-cause)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/vibe-flake-root-cause"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-flake-root-cause/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/vibe-flake-root-cause"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-flake-root-cause.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.00096 | $0.00738 |
| Opus 5.5 | $0.00038 | $0.00295 |
| Sonnet 5.5 | $0.00019 | $0.00148 |
| Haiku 4.5 | $0.00010 | $0.00074 |
Grade A, and why
vibe-flake-root-cause 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 17d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-flake-root-cause
"Flaky" ends an investigation without finding anything, and a retry-to-green hides real defects. An intermittent failure is a hypothesis: some variable you haven't controlled decides the outcome. Find it, force it, and prove the fix with counts.
When to Use This Skill
- "It passed on rerun"
- A failure that shows up only in CI
- A threshold (performance, visual diff, timeout) that fails on some runs
- You're tempted to add a retry, raise a timeout, or loosen a tolerance
When NOT to Use This Skill
- The failure reproduces every time (debug it directly)
- Race conditions visible in the test code itself (use
vibe-concurrent-test-safety) - The job died before any test ran (checkout, install, runner loss); a single re-run is fine there, but say so
Steps
-
Record the failure exactly. Commit, environment, profile or device, the failing value, and the threshold. Keep the log.
-
Run it alone, cleanly. If it passes in isolation, treat it as contention until proven otherwise, and name the resource: CPU, a shared port, a shared database, disk, or network. Record machine load alongside every timing measurement.
-
List candidate variables and force each in turn. Common ones:
- timing: network latency, font or asset arrival, animation frames
- environment: CPU load, parallel agents or tests, shared ports and servers
- data: ordering, time of day, random seeds, page or payload size
- process mode: a server started in a mode the framework doesn't support in production
-
Reproduce at a stated rate before changing anything (for example "10 of 15 runs fail with fonts held back 600 ms"). No reproduction means no root cause yet, so keep looking or report it as unresolved.
-
Fix the cause, not the symptom. Then rerun the forced condition N times and report the new rate (for example "0 of 240 loads across 4 routes").
-
Disclose any mitigation. If you clip, retry, or quarantine anything, say what, why, and why it doesn't hide a defect. Never widen a threshold or budget to pass (
vibe-anti-rationalization-check).
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.
- 17d ago First seen · 57 lines · 96 tokens per session scan A 93e43f99442c
vibe-flake-root-cause is a skill published in the GitHub repository ash1794/vibe-engineering (164 stars, last pushed 9d ago), licensed MIT. It adds 96 tokens to every session and 738 once invoked, about $0.0004 per session on Opus 5.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-09-29.
Other skills, from other repositories
unica-testing
A testing guide for Unica, covering how to choose, write, run, and review tests in Rust and Python. It also explains test boundaries, test sizes, Rust nextest, Python unittest, and failure analysis.
generator-apply-fixes
Internal Auto-Harness generator skill for QA fix cycles. Use only inside the Generator subagent when it is addressing named defects from QA or retest.
gut
Godot Unit Testing (GUT) framework for GDScript. Covers test structure, assertions, doubles/mocks, async testing, memory management, and CLI execution. Use when writing tests, understanding test patterns, or troubleshooting test failures.
health
Audits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.
cherry-electron-dev
Develop, fix, profile, and test PRs in a tracked Cherry Studio Electron instance. Use for implementation, UI and interaction work, runtime debugging, DevTools inspection, performance analysis, and interactive PR verification with a test report. Reuse a verified workspace instance and manage its lifetime according to…
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.