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 shabaraba/vibing.nvim --skill ci-gatesgit clone --depth 1 https://github.com/shabaraba/vibing.nvimWrote 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/shabaraba/vibing.nvim/ci-gates)<a href="https://agentmods.dev/skills/shabaraba/vibing.nvim/ci-gates"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/ci-gates/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/shabaraba/vibing.nvim/ci-gates"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/ci-gates.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.00107 | $0.02526 |
| Opus 5.5 | $0.00043 | $0.01010 |
| Sonnet 5.5 | $0.00021 | $0.00505 |
| Haiku 4.5 | $0.00011 | $0.00253 |
Grade A, and why
ci-gates 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 15d 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Gates for vibing.nvim
Every gate in this repository has, at some point, passed over a broken tree. Each section below is
one of those failures and the shape that now prevents it. Meta-tests (tests/*.test.mjs) pin the
gates themselves; when you change a gate, change its meta-test in the same edit.
The CI Gate Is the Exit Code
CI runs npm run test:lua and reads nothing but its exit status. Do not add output parsing back:
PlenaryBustedDirectory prints one summary per spec file, so any grep for Failed : 0
matches while other files are failing — which is exactly how the gate passed a run with five dead
specs (#561). tests/lua-test-exit-code.test.mjs pins the three cases the gate rests on: a failing
assertion, a spec that will not load, and an otherwise-passing run.
The one case neither the exit code nor a summary count catches is a spec file that runs zero
tests (a describe that stopped being reached): plenary exits 0 without printing a summary, which
is also how the E2E specs opt out via should_run().
A Spec Cannot Outlast Its Harness
PlenaryBustedDirectory runs one child Neovim per spec file and joins it with a single
timeout — 50000ms unless the invocation says otherwise. A spec still inside a vim.wait when that
expires is killed mid-wait: no summary, no failure, no test count. Only the exit code moves, which
is the zero-tests shape above arriving by a different route.
Three E2E specs sat in exactly that state, each budgeting ASSISTANT_RESPONSE = 60000 against the
50000ms default: they died at 50.2s every run and printed nothing at all. test:e2e now passes
timeout = 240000, and tests/e2e-timeout-gate.test.mjs keeps the two numbers in agreement — it
reads the budget out of the test:e2e command itself (so it cannot pass against a command the
project no longer runs) and sums every wait each spec file can perform. The sum is deliberately an
over-estimate; over-counting only ever asks for a larger budget, and an exact model is what would
let the silent case back in. The bound is per file, not per test, because the timeout is on
the job.
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.
- 15d ago Changed · +1 lines 88bdf35de78a
- 1mo ago Changed · +62 lines · +16 tokens per session 94a3aa299b66
- 1mo ago First seen · 94 lines · 91 tokens per session scan A 53b2ce5cf841
ci-gates is a skill published in the GitHub repository shabaraba/vibing.nvim (13 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 2,526 once invoked, about $0.0004 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-05.
Other skills, from other repositories
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
ci-quarantine
Put a known-flaky test into, or take it out of, CI Steward's quarantine lane: it keeps running and reporting but cannot fail the merge queue. Use when a test that passes on retry keeps ejecting green PRs, when an entry is about to expire, or when a quarantined test is fixed and should block again.
prove-the-gates
Audit the repository's own checks — for each test, gate and CI script, establish what it guards, whether anything still runs it, and whether it actually fails when you break what it protects. Use when the user says "prove the gates", "are our tests real", "audit the test suite", "which checks are fake", "תוכיח את…
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
sweep-reds
Repair confirmed CI failures base-first, then prepare affected PRs one at a time with exact-candidate evidence. Use when asked to sweep reds or restore the queue. Never merges, closes PRs, weakens tests, or changes CI under ordinary sweep authority.
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.