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 agentmods add skills/mracal/vibe-engineering/gap-analysisnpx skills add mracal/vibe-engineering --skill gap-analysisgit 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-analysis)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/gap-analysis"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/gap-analysis.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.01358 |
| Opus 5 | $0.00018 | $0.00679 |
| Sonnet 5 | $0.00007 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
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 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.
This is a copy
100% identical to vibe-gap-analysis — 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 — 144 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.
- Read architecture/design docs in
docs/or similar - Read implementation code in
src/,internal/,lib/etc. - Compare implementation against architecture doc section by section
- 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
- Produce structured gap report: component, expected status, actual status, % complete, action items
- Save to
docs/plans/gap-analysis-$(date +%Y%m%d).md - Commit with
docs: gap analysis $(date +%Y%m%d)
Deep (--deep)
Full 17-dimension audit using parallel subagents. Exhaustive production readiness assessment.
Dispatch parallel agents (model: sonnet) in 3 rounds:
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.
- 4d ago First seen · 144 lines · 36 tokens per session scan A 092ddcd537ea
vibe-gap-analysis is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 1,358 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-gap-analysis, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
add-agent-support
Create and ship AgentSessions support for a new or changed local AI agent/provider. Use when adding, reviewing, testing, documenting, or marketing a provider integration, session parser, transcript source, support-matrix entry, verified-version bump, or provider UI surface; drives the full loop from pre-support…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.