vibe-gap-closure-loop

vibe-gap-closure-loop is a skill for Claude Code, Codex from ash1794/vibe-engineering. It costs 45 tokens per session (1,433 once invoked), scanned A, original, MIT.

An automation loop for fixing findings in a production-readiness report, which lists work still needed before software is ready for release. It organizes the findings, assigns work, runs tests, checks the results again, and repeats toward target scores.

In plain words
What is it for?
Use it after a gap analysis with at least ten findings, especially when the findings can be worked on independently. It is not intended for a small number of issues or major architectural redesigns.
Why use it?
It helps manage many outstanding issues across different parts of a system instead of treating them as one unstructured to-do list.

Skill for Claude CodeCodex

Part of the vibe-engineering plugin — 38 skills shipped together

Install

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.

agentmods
npx agentmods add skills/ash1794/vibe-engineering/gap-closure-loop
Any agent
npx skills add ash1794/vibe-engineering --skill gap-closure-loop
Clone the repo
git clone --depth 1 https://github.com/ash1794/vibe-engineering

Made for: Claude Code, Codex.

Or install vibe-engineering, the plugin that ships this one along with the rest of its 38 skills.

Wrote 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.

agentmods badge for vibe-gap-closure-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/ash1794/vibe-engineering/gap-closure-loop.svg)](https://agentmods.dev/skills/ash1794/vibe-engineering/gap-closure-loop)
Your own site
<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/gap-closure-loop"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/gap-closure-loop.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,433 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.01433
Opus 5 $0.00023 $0.00717
Sonnet 5 $0.00009 $0.00287
Haiku 4.5 $0.00005 $0.00143

Measured 4d ago against content hash e8fd882c6f7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/vibe-engineering/skills/gap-closure-loop/SKILL.md · 167 lines

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-analysis and 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-design first)
  • When you don't have a gap analysis document yet (run vibe-gap-analysis first)

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: latest gap-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"];
}

Read the full file on GitHub · 167 lines

Changes

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.

  1. 4d ago First seen · 167 lines · 45 tokens per session scan A e8fd882c6f7a

Subscribe to this mod's changes

vibe-gap-closure-loop is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,433 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.

Related

Other skills, from other repositories

wechat-article-writer

公众号/自媒体全流程。根据用户表述自动匹配:撰写文章、封面图、正文插图、风格提取。支持多种写作风格。当用户提到写公众号、技术博客、公众号封面、正文插图、步骤图、演示图、流程示意、分析写作风格、克隆文风、模仿爆款、提取风格时使用。详见 reference 目录。.

xstongxue/best-skills · 105 tokens

prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.

CherryHQ/cherry-studio · 44 tokens

find-skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

CherryHQ/cherry-studio · 67 tokens

cherry-assistant-guide

从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本,或报告运行错误、连接失败、配置异常并需要诊断时触发。.

CherryHQ/cherry-studio · 68 tokens

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…

CherryHQ/cherry-studio · 75 tokens

issue-reporter

只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitHub 时不得触发,必须改用 cherry-studio-feedback 并默认提交飞书。.

CherryHQ/cherry-studio · 73 tokens