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 Totes-MickGOATs/opus-pocus --skill nihil-reveliogit clone --depth 1 https://github.com/Totes-MickGOATs/opus-pocusWrote 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/totes-mickgoats/opus-pocus/nihil-revelio)<a href="https://agentmods.dev/skills/totes-mickgoats/opus-pocus/nihil-revelio"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/nihil-revelio/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/totes-mickgoats/opus-pocus/nihil-revelio"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/nihil-revelio.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.00155 | $0.01578 |
| Opus 5 | $0.00077 | $0.00789 |
| Sonnet 5 | $0.00031 | $0.00316 |
| Haiku 4.5 | $0.00015 | $0.00158 |
Grade A, and why
nihil-revelio 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 12d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🐉 Nihil Revelio
"It scanned nothing. It said 'clean.' Those are different words."
An unexercised check is blind, not clean. A check that cannot distinguish "I looked and found nothing" from "I never looked" reports the same success for both, and the second one is the state that ships defects. This is the most expensive class of automation defect because it inverts the tool's purpose: the green verdict is not merely uninformative, it is actively misleading, and it is trusted precisely when it should not be.
What to scan
- Every lint, gate, verifier and test-runner wrapper the repo carries
- Their verdict logic: what they print, what they exit with, and how the two relate
- Every caller that reads one of those verdicts — a caller reading an exit code where the artifact is the evidence is half the defect
- Filter and selector arguments, and what a non-matching filter produces
- Test suites for the checks themselves: is each verdict state exercised by a case?
Vendor tools are out of scope; their invocation is in scope. You cannot add a verdict state to
eslint, pytest, tsc or go test — what you own is the line that calls them and the step that
reads the result, so audit that. On a repo whose checks are all vendor tools, the instances of this
class look like:
- a CI step whose file glob matched nothing and exited 0 (
eslint $CHANGEDwith$CHANGEDempty) - a test run that collected zero tests and reported success — a typo'd
pytest -kexpression,go test ./internal/...on a package that moved, a JesttestPathPatternmatching nothing - a
continue-on-error: truestep whose failure the rollup then reports as green - a coverage gate reading an artifact that was never written
Prescribe the guard on the caller: assert a non-empty input set before invoking, assert a
non-zero collected-test count after (pytest --co -q | tail -1, jest --listTests | wc -l), and
assert the results file exists and is newer than its inputs. If the repo's only checks are vendor
tools invoked with no such assertion, that is one finding, not seven.
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.
- 12d ago First seen · 90 lines · 155 tokens per session scan A 0ab7429965e4
nihil-revelio is a skill published in the GitHub repository Totes-MickGOATs/opus-pocus (10 stars, last pushed 1mo ago), licensed MIT. It adds 155 tokens to every session and 1,578 once invoked, about $0.0008 per session on Opus 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
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.