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 acceptance-gategit 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/acceptance-gate)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/acceptance-gate"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/acceptance-gate.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.1 | $0.00037 | $0.00451 |
| Opus 5 | $0.00018 | $0.00226 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
vibe-acceptance-gate 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 7d 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-acceptance-gate — 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.
What it actually says
vibe-acceptance-gate
Don't claim "done" until you've checked against the criteria that define "done."
When to Use This Skill
- After completing a task that has acceptance criteria
- Before marking an issue/ticket as resolved
- When the user asks "is this done?"
- After implementing a spec with defined requirements
When NOT to Use This Skill
- Exploratory work with no defined criteria
- Research tasks (use
vibe-reflect-and-compoundinstead) - When criteria haven't been defined yet (define them first)
Steps
-
Find the criteria — Look in:
- Issue/ticket description (MUST/SHOULD requirements)
- Spec document (acceptance criteria section)
- Task description (success conditions)
- User's original request (implicit criteria)
-
Validate each criterion — For each one:
- Run the relevant test, command, or check
- Record PASS (met), FAIL (not met), or PARTIAL (partially met)
- Capture evidence (test output, code reference)
-
Report results:
| # | Criterion | Status | Evidence |
|---|---|---|---|
| 1 | [criterion text] | PASS/FAIL/PARTIAL | [evidence] |
- Gate decision:
- All PASS → Task complete
- Any FAIL on MUST criteria → Task NOT complete, list remaining work
- PARTIAL only → Report what's missing, ask user if acceptable
Output Format
Acceptance Gate: [Task Name]
Result: PASS / FAIL / PARTIAL Criteria Met: X/Y (Z%)
| # | Criterion | Status | Evidence |
|---|---|---|---|
| 1 | ... | ✓/✗/◐ | ... |
Remaining Work (if FAIL)
- [What needs to be done]
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.
- 7d ago First seen · 61 lines · 37 tokens per session scan A 96136c363aa2
vibe-acceptance-gate is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 451 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-acceptance-gate, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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.
build-and-runtime-verification
Use when running build, compile, test, launch, or runtime checks and producing a verdict tied to exact commands, exit codes, artifact paths, limitations, and fresh evidence.
load-soak-capacity-verification
Use when servers or online game services need controlled load, soak, concurrency, capacity, saturation, leak, queue, failover, recovery, and scaling verification with baselines and stop conditions; not for client frame budgets.
platform-device-compatibility-matrix
Use when a game needs a platform and device compatibility matrix across OS, hardware, GPU, memory, resolution, input, network, storefront, certification, test evidence, and support policy; not for store metadata preparation.
playtest-evidence
Use when planning or reviewing game playtests that need structured scenarios, participant context, observations, reproduction evidence, severity, and honest separation of observed findings from conclusions.
qa-test-strategy-and-coverage
Use when a game project, milestone, or feature needs a QA test strategy and coverage matrix across risk, test levels, platforms, environments, ownership, automation, regression, evidence, and exit criteria; not for one playtest session.