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 agentmods add skills/agent-rig/rig/rig-proofnpx skills add agent-rig/rig --skill rig-proofgit clone --depth 1 https://github.com/agent-rig/rigWhat 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 | $0.00127 | $0.02094 |
| Opus 5 | $0.00063 | $0.01047 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 173 lines · 127 tokens per session scan A b0588afed179
rig-proof is a skill published in the GitHub repository agent-rig/rig (2 stars, last pushed 14d ago), licensed MIT. It adds 127 tokens to every session and 2,094 once invoked, about $0.0006 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
audit-onboarding-proposal
Independently audit a brownfield onboarding transcript, operational map, or exact proposed documentation patch before application. Use when a fresh reviewer must verify an $onboard-repository first pass, distinguish environment-caused Unknowns from reasoning defects, score its safety and evidence gates, or run a…
engineering-wisdom
Provide an explicitly requested, repository-grounded engineering review using contextual heuristics for code clarity, SOLID and design, testing, refactoring, architecture, and professional practice. Use only when the user invokes $engineering-wisdom or explicitly asks for this installed engineering-wisdom pack; do not…
red-team-adversarial
Adversarial security and resilience analysis — auto-triggered during /review and /test based on task classification. Provides attack surface analysis, boundary testing, auth bypass attempts, dependency chain attacks, and Beast Mode stress testing.
product-decision-agent
中文产品决策 Agent。用于中国大陆互联网产品、运营、增长、商业化、数据、项目推进和组织协作场景：产品规划、需求分析、PRD、需求优先级、排期、版本规划、Roadmap、MVP、灰度、上线、迭代、增长停滞、拉新、投放、渠道、裂变、CAC、LTV、ROI、留存、转化、DAU/MAU、GMV、漏斗、社区运营、内容供给、创作者、用户运营、活动运营、私域、会员、定价、指标异常、数据口径、埋点、A/B…
marketing-copy
Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.