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 rexleimo/aios --skill verification-loopgit clone --depth 1 https://github.com/rexleimo/aiosWrote 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/rexleimo/aios/verification-loop)<a href="https://agentmods.dev/skills/rexleimo/aios/verification-loop"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/verification-loop/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/rexleimo/aios/verification-loop"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/verification-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01290 |
| Opus 5.5 | $0.00013 | $0.00516 |
| Sonnet 5.5 | $0.00006 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
verification-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 3d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Loop
Trigger
Use this skill when:
- You changed runtime behavior (scripts, wrappers, MCP server, install flows)
- You are about to say "done", "fixed", "works", or "passes"
- You are about to bump version / release
Rules
- Prefer commands with deterministic exit codes over "it looks fine".
- If you cannot run verification, say exactly what you could not run and why.
Baseline Checks (AIOS)
-
Run the verifier:
aios doctor- Or:
aios doctor - Compatibility wrappers:
scripts/verify-aios.sh/scripts/verify-aios.ps1
-
MCP server changes (minimum):
cd mcp-server && npm run typecheckcd mcp-server && npm run build- Manual smoke:
chrome.launch_cdp->browser.connect_cdp->page.goto->page.extract_text/page.screenshot->browser.close
-
Install/wrapper changes:
- Re-run install/update on a clean-ish shell session.
- Confirm new commands are visible and resolve to
ROOTPATHscripts.
Evidence Capture
- Record the exact commands run and whether they succeeded.
- For failures: include the first actionable error line and the remediation you applied.
Structured Verdict Schema
Inspired by the-pair v2.0.2 quality_gate.rs: every completion claim MUST be
backed by a structured verdict with exactly four sections. A verdict missing any
section is an automatic REJECT — there is no partial credit.
The four required sections, in order:
- FILES_REVIEWED — list of files reviewed with line ranges and change status.
- CHECKS — typecheck, test suite, lint — each with a concrete PASS/FAIL status.
- CODE — the specific code snippet or issue reference, as a quoted block.
- VALIDATION — summary verdict:
APPROVEDorREJECTED, withscore,complete, andmissing[]. When rejected,missingfeeds the next round directly, plus specificnext_actions.
Mandatory format
VERDICT:
FILES_REVIEWED:
- path/to/file.ts: lines 45-67 (changed)
CHECKS:
- typecheck: PASS
- test suite: PASS (8/8)
- lint: PASS
CODE:
> // specific snippet or issue reference
VALIDATION:
APPROVED — score: 1.0, complete: true, missing: []
OR
REJECTED — score: <0-1>, complete: false,
missing:
- [specific gap feeding the next round]
next_actions:
- [specific, actionable step per gap]
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.
- 3d ago Changed 10629b7d1b61
- 27d ago Changed f9ac3b323581
- 1mo ago Changed b5f749d84755
- 1mo ago Changed 4a802d79a13d
- 1mo ago Changed · +31 lines 9ff50d15a597
- 1mo ago First seen · 102 lines · 32 tokens per session scan A 16cd990ddd02
verification-loop is a skill published in the GitHub repository rexleimo/aios (54 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,290 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
verify-work
Prove that code, a script or a page you just produced actually runs — execute it, read the real output, and fix what breaks before reporting. Use after writing or changing anything executable, and whenever you are about to say something is done, working, or fixed.
BrowserBash Browser Automation
BrowserBash is a vendor-independent, natural-language browser automation CLI. Drive a real browser from plain-English objectives or committable Markdown tests, run on local Chrome, CDP/Playwright MCP, Browserbase, LambdaTest, or BrowserStack, and stream NDJSON results with CI exit codes — using free local Ollama…
verify
Prove a completion claim with fresh evidence before making it — the gate's exit code, the real diff, the remote's checks, the reviewer's verdict.
checking-a-page
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
codexkit-test-hardening
Strengthen test coverage around changed behavior, edge cases, and regressions without writing noisy or brittle tests.
testing-standards
Invoke when writing tests, reviewing test quality, or setting up test infrastructure. Contains project-specific testing framework conventions, fixture patterns, and coverage expectations.