agentmods.dev

vibe-gap-analysis

vibe-gap-analysis is a skill for Claude Code from ash1794/vibe-engineering. It costs 65 tokens per session (1,467 once invoked), scanned A, original, MIT.

A codebase audit skill that compares architecture or product specifications with the implementation and reports missing or incomplete work. It offers a quick check, a deeper 17-area audit, or a review of selected areas.

In plain words
What is it for?
Use it to assess production readiness, verify that a refactor preserved required behavior, or compare documented plans with the code.
Why use it?
It helps identify gaps before release, after a major refactor, or when taking over an unfamiliar codebase.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

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

not rated 164repo +1 changed 8d ago A scan 65 tokens original MIT

Good fit Use it to assess production readiness, verify that a refactor preserved required behavior, or compare documented plans with the code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ash1794/vibe-engineering/vibe-gap-analysis
View source ↗ ash1794/vibe-engineering
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.

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

Made for: Claude Code.

Or install vibe-engineering, the plugin that ships this one along with the rest of its 33 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-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-gap-analysis/github.svg)](https://agentmods.dev/skills/ash1794/vibe-engineering/vibe-gap-analysis)
Your own site
<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/vibe-gap-analysis"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-gap-analysis/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.

agentmods 80×15 button for vibe-gap-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/vibe-gap-analysis"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-gap-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,467 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00065 $0.01467
Opus 5.5 $0.00026 $0.00587
Sonnet 5.5 $0.00013 $0.00293
Haiku 4.5 $0.00006 $0.00147

Measured 8d ago against content hash 0ad87da8f073, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibe-gap-analysis 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 8d 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/vibe-gap-analysis/SKILL.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

vibe-gap-analysis

Cynical gap analysis comparing specs/architecture to actual implementation. Three modes from fast to exhaustive. Works with any project that has architecture docs and implementation code.

When to Use This Skill

  • Before launching to production
  • After a major refactor to verify nothing was lost
  • When inheriting a codebase and need to assess completeness
  • Periodic production readiness audits
  • When stakeholders ask "how done are we?"

When NOT to Use This Skill

  • Greenfield projects with no specs yet (write specs first)
  • Simple bug fixes or feature additions
  • Frontend-only or design-only reviews

Usage

/vibe-gap-analysis              # Quick static (5 structural dimensions)
/vibe-gap-analysis --deep       # Full 17-dimension audit with parallel agents
/vibe-gap-analysis --dim N      # Single dimension deep-dive (1-17)
/vibe-gap-analysis --dim 1,4,9  # Multiple specific dimensions

Modes

Quick Static (default)

Fast, single-agent structural audit. No subagents dispatched.

  1. Read architecture/design docs in docs/ or similar
  2. Read implementation code in src/, internal/, lib/ etc.
  3. Compare implementation against architecture doc section by section
  4. Cover dimensions 1-5 (structural):
    • Dim 1: Spec Compliance — check specs against implementation
    • Dim 2: Backend Code Quality — test coverage, error handling, lint issues
    • Dim 3: Frontend Completeness — UI components, routes, test coverage
    • Dim 4: Deployment & Ops — deploy scripts, CI/CD, Docker, TLS
    • Dim 5: Architecture Integrity — design pattern compliance, component boundaries
  5. Produce structured gap report: component, expected status, actual status, % complete, action items
  6. Save to docs/plans/gap-analysis-$(date +%Y%m%d).md
  7. Commit with docs: gap analysis $(date +%Y%m%d)

Deep (--deep)

Full 17-dimension audit using parallel subagents where the harness supports them (Claude Code, Codex, and Gemini CLI all can). Without subagents, run the dimensions sequentially. Exhaustive production readiness assessment.

Read the full file on GitHub · 145 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. 8d ago Changed · +29 tokens per session 0ad87da8f073
  2. 20d ago First seen · 145 lines · 36 tokens per session scan A 2423d23c6a60

Subscribe to this mod's changes

vibe-gap-analysis is a skill published in the GitHub repository ash1794/vibe-engineering (164 stars, last pushed 8d ago), licensed MIT. It adds 65 tokens to every session and 1,467 once invoked, about $0.0003 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-26.

Claude CodeCode reviewPlanningTestingclaude-code-plugindeveloper-toolsskillsvibe-coding
Related

Other skills, from other repositories

pre-pr-audit

Pre-PR confidence audit with 5-dimension scoring. Use when: final check before commit/push/PR, evaluating PR readiness, assessing test quality + risk + coverage holistically. Triggers: pre-pr, readiness check, confidence audit, final verification, ready to PR, how confident. Not for: code review (use…

sd0xdev/sd0x-harness · 95 tokens

brooks-test

Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…

hyhmrright/brooks-lint · 161 tokens

test-review

Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.

sd0xdev/sd0x-harness · 56 tokens

precommit

Pre-commit checks — lint:fix -> build -> test.

sd0xdev/sd0x-harness · 15 tokens

pr-comment

Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).

sd0xdev/sd0x-harness · 67 tokens

precommit-fast

Quick pre-commit checks — lint:fix -> test.

sd0xdev/sd0x-harness · 15 tokens