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 agent-rig/rig --skill rig-proofgit clone --depth 1 https://github.com/agent-rig/rigWrote 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/agent-rig/rig/rig-proof)<a href="https://agentmods.dev/skills/agent-rig/rig/rig-proof"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-proof/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/agent-rig/rig/rig-proof"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-proof.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.00127 | $0.02094 |
| Opus 5.5 | $0.00051 | $0.00838 |
| Sonnet 5.5 | $0.00025 | $0.00419 |
| Haiku 4.5 | $0.00013 | $0.00209 |
Grade A, and why
rig-proof 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 1mo 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rig-proof — proofread what an agent wrote
Two verbs over one source of truth:
find(default) — check prose against the project's writing-style guide and return findings with line references. Read-only.fix— apply them, then re-check.
The guide is the only rulebook. Its path is style.guideFile in
.rig/config.json (default .claude/STYLE.md). This skill has no style
opinions of its own: read the guide, walk its rules, cite them by number. When a
project prunes or extends the guide, this skill follows automatically — the same
relationship /rig-review has to REVIEWER.md.
Why this exists
The personas already tell agents how to write. Instructions decay under load: an
agent 40 tool-calls deep, writing the PR body last, has spent its attention
elsewhere. This is the gate that catches what the instruction missed — the same
reason /rig-task runs a pre-PR self-review instead of trusting that the coder
internalized the review catalog.
Configuration
Reads .rig/config.json:
style.guideFile— the writing-style guide, and the only rule source (default.claude/STYLE.md, then.rig/STYLE.md). If no guide is found, say so and stop — don't substitute your own preferences.vcs.baseRef— diff base when checking changed Markdown (defaultorigin/main).project.repo—owner/nameforghcalls when the target is a PR.
Scope — what to check, and what to leave alone
Default to one named target. This skill is a proofreader, not a repo-wide linter; pointing it at every document in the tree produces a finding pile nobody asked for.
Resolve $ARGUMENTS to a target in this order:
| Argument | Target |
|---|---|
| a file path | that file |
--stdin, or prose pasted into the request |
that text |
a PR number, or pr |
the PR body (gh pr view <n> --json body -q .body) |
| an issue/ticket ID | that ticket's description |
--base <ref>, or diff |
Markdown files changed vs <ref> |
| nothing | ask what to check — don't guess, and don't default to the repo |
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.
- 1mo ago First seen · 173 lines · 127 tokens per session scan A b0588afed179
rig-proof is a skill published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 127 tokens to every session and 2,094 once invoked, about $0.0005 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
proxmox-full
Complete Proxmox VE hypervisor management via REST API - VMs, containers, snapshots, backups, storage.
a-philosophy-of-software-design
Apply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.
aerodynamicist
Think and work like an expert Aerodynamicist. Use when a task calls for Aerodynamicist judgment. Reasons from circulation, Cp distributions, and boundary-layer physics through Re/Mach similitude, NACA airfoil polars, stall classification, wind-tunnel blockage/wall corrections, and SA/SST/LES external-aero CFD—not…
agronomist
Think and work like an expert Agronomist. Use when a task calls for Agronomist judgment. Reasons from 4R stewardship and G×E×M through MRTN economic N, calibrated soil-test extractants, penetrometer compaction diagnosis, on-farm strip mixed models, partial budgets, and AgroEcoList reporting while treating…
algebraist
Think and work like an expert Algebraist. Use when a task calls for Algebraist judgment. Reasons from carriers, operations, and morphisms through isomorphism theorems, universal properties, exact-sequence and homological tools (Ext, Tor, snake lemma), and computational systems like GAP, Magma, SageMath, and Lean while…
astrodynamicist
Think and work like an expert Astrodynamicist. Use when a task calls for Astrodynamicist judgment. Reasons from two-body plus perturbation force models through Cowell/Encke propagation, batch LS and EKF orbit determination, SPICE/Horizons ephemerides, CCSDS OEM/CDM exchanges, and TEME–GCRF frame discipline while…