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 CoriChui/yolo --skill yolo-verifygit clone --depth 1 https://github.com/CoriChui/yoloWrote 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/corichui/yolo/yolo-verify)<a href="https://agentmods.dev/skills/corichui/yolo/yolo-verify"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-verify/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/corichui/yolo/yolo-verify"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-verify.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.00063 | $0.00439 |
| Opus 5.5 | $0.00025 | $0.00176 |
| Sonnet 5.5 | $0.00013 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
yolo-verify 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 2d 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.
What it actually says
yolo-verify
Decide, with evidence, whether feature/<slug> satisfies its brief. Rules:
../../yolo/conventions.md.
Inputs
workspace/features/<slug>/brief.md→success_criteria.- The branch's own changes:
git diff <base>...feature/<slug>(three-dot). - The project's lint and test commands. Find them in
package.jsonscripts, aMakefile,justfile,pyproject.tomlor CI config. If there are none, say so; don't invent any.
Procedure
- Check out
feature/<slug>and make sure the working tree is clean. - Run the lint and test commands. Record pass/fail and the key output.
- For each criterion, gather concrete evidence: a passing test, an observed behavior, a code reference. Mark it met or unmet. A criterion you couldn't actually check is unmet.
- Write
workspace/features/<slug>/verification.md: one section per criterion with its evidence, then the lint/test results.
Outcome
- All met: commit only that file, with the trailer, as the branch tip:
git add workspace/features/<slug>/verification.md && git commit -m "yolo: verify <slug>" --trailer "YOLO-Verified: true". Status readsverifieduntil the branch is merged. Any later commit on the branch makes the verification stale; re-run this skill before merging. - Any unmet: still write
verification.md(it records the gap), commit it without the trailer, and report what failed.
Constraints
- Writes only
verification.md. Never edits code to make a criterion pass.
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.
- 2d ago Changed · +9 lines · +1 tokens per session b70136e1c0cd
- 1mo ago First seen · 26 lines · 62 tokens per session scan A 73b8371980e1
yolo-verify is a skill published in the GitHub repository CoriChui/yolo (9 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 439 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-08-31.
Other skills, from other repositories
hermit-scribe
File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
mean-tester
Mean test another agent when someone asks you to test, check or break it. Invoke on "test @agent", "mean test @agent", "check whether @agent works", on "continue " or "rerun " in a new message, or on "continue" in a thread where you already reported a campaign, and on "Judge this recorded exchange".
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
implement
Implement a ticket or feature with proportional planning, test first behavior changes, independent review when available, and verification through the real affected surface.
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".