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 gap-closure-loopgit 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/gap-closure-loop)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/gap-closure-loop"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/gap-closure-loop/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/gap-closure-loop"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/gap-closure-loop.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.00045 | $0.01433 |
| Opus 5.5 | $0.00018 | $0.00573 |
| Sonnet 5.5 | $0.00009 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
vibe-gap-closure-loop 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 2mo 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-gap-closure-loop — 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-gap-closure-loop
Autonomous loop that closes gap analysis findings to a target score. Dispatches parallel agents per work stream, runs test gates, re-audits, and repeats. Designed for YOLO mode — no confirmation between phases.
When to Use This Skill
- After running
vibe-gap-analysisand receiving a gap report - When you have 10+ findings to close systematically
- When findings span multiple system areas that can be parallelized
- Production readiness sprints
When NOT to Use This Skill
- Fewer than 5 findings (just fix them directly)
- Findings that require architectural redesign (needs
vibe-research-before-designfirst) - When you don't have a gap analysis document yet (run
vibe-gap-analysisfirst)
Arguments
/vibe-gap-closure-loop [dimensions] [--target N] [--gap-file PATH]
dimensions: Which dimensions to close (default:1-12)--target: Target score per dimension (default:95)--gap-file: Path to gap analysis (default: latestgap-analysis-*.md)
Loop Flow
digraph gap_closure {
rankdir=TB;
"Read gap analysis" [shape=box];
"Dependency analysis" [shape=box];
"Group into work streams" [shape=box];
"Dispatch execution agents" [shape=box];
"Barrier: wait for all" [shape=box];
"Run tests" [shape=box];
"Tests pass?" [shape=diamond];
"Fix failures" [shape=box];
"Write iteration summary" [shape=box];
"All dimensions at target?" [shape=diamond];
"Done — commit & report" [shape=doublecircle];
"Read gap analysis" -> "Dependency analysis";
"Dependency analysis" -> "Group into work streams";
"Group into work streams" -> "Dispatch execution agents";
"Dispatch execution agents" -> "Barrier: wait for all";
"Barrier: wait for all" -> "Run tests";
"Run tests" -> "Tests pass?";
"Tests pass?" -> "Write iteration summary" [label="yes"];
"Tests pass?" -> "Fix failures" [label="no"];
"Fix failures" -> "Run tests";
"Write iteration summary" -> "All dimensions at target?";
"All dimensions at target?" -> "Done — commit & report" [label="yes"];
"All dimensions at target?" -> "Dependency analysis" [label="no — next iteration"];
}
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.
- 2mo ago First seen · 167 lines · 45 tokens per session scan A e8fd882c6f7a
vibe-gap-closure-loop is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 18d ago), licensed MIT. It adds 45 tokens to every session and 1,433 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-gap-closure-loop, 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.
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-client-offline-debugging
Use when a Unity client cannot enter offline gameplay because login, bootstrap, disconnected server handling, local mock data, network fallback, or scene startup paths fail.
unity-ui-rendering-debugging
Use when a Unity UI, HUD, screen item, or NGUI widget is missing, clipped, behind another canvas, wrongly sorted, disconnected from a prefab or atlas, misanchored, or invisible despite correct gameplay state.
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.