rig-tidy

rig-tidy is a skill for Claude Code from agent-rig/rig. It costs 56 tokens per session (802 once invoked), scanned A, original, MIT.

A post-merge cleanup procedure that reviews recent code changes for unused code, repeated code, outdated comments, and unused imports, then removes safe findings. A merge combines changes into a shared code branch.

In plain words
What is it for?
Use it after merging work to inspect a chosen directory and recent commits, clean obvious clutter, and run the project's tests.
Why use it?
It catches small maintenance problems that can remain after fast development or after several changes are combined.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Good fit Use it after merging work to inspect a chosen directory and recent commits, clean obvious clutter, and run the project's tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agent-rig/rig/rig-tidy
Install

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.

Any agent
npx skills add agent-rig/rig --skill rig-tidy
Clone the repo
git clone --depth 1 https://github.com/agent-rig/rig

Made for: Claude Code.

Wrote 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.

agentmods badge for rig-tidy

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent-rig/rig/rig-tidy/github.svg)](https://agentmods.dev/skills/agent-rig/rig/rig-tidy)
Your own site
<a href="https://agentmods.dev/skills/agent-rig/rig/rig-tidy"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-tidy/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.

agentmods 80×15 button for rig-tidy

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-rig/rig/rig-tidy"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-tidy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 802 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.00802
Opus 5.5 $0.00022 $0.00321
Sonnet 5.5 $0.00011 $0.00160
Haiku 4.5 $0.00006 $0.00080

Measured 1mo ago against content hash a59c0437531c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rig-tidy 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.

skills/rig-tidy/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Post-Merge Cleanup

Audit and clean up the diff from the last N commits. Catches dead code, unused imports, stale comments, and obvious duplicates that slipped in during rapid development.

Configuration

Reads .rig/config.json:

  • sourceScope[0] — the default directory to audit when no scope is given (default: src).
  • test.command — the suite run in the verify step (default: npm test).
  • agents.reviewer — the project's name for the canonical reviewer role (default: reviewer).

If the file is absent, use the defaults above and note you're running unconfigured.

Arguments

The user invoked this with: $ARGUMENTS

What to do

  1. Parse the arguments.

    • scope: directory to audit (default: the default source scope from .rig/config.json (sourceScope[0], default src)).
    • commits: number of recent commits to review (default: 10)

    Examples:

    • /rig-tidy → default scope, 10 commits
    • /rig-tidy path/to/dir 5 → that directory, 5 commits
    • /rig-tidy 20 → default scope, 20 commits
  2. Show what will be audited.

    git log --oneline -${commits}
    git diff HEAD~${commits} --stat -- ${scope} | tail -20
    
  3. Audit the diff via a fresh-context subagent. Spawn a reviewer agent (mapped through agents.reviewer) with this prompt (don't do the audit inline — the implementer context is too close to the code to spot dead-on-arrival abstractions):

    "Audit the diff git diff HEAD~${commits} -- ${scope} for cleanup candidates. Categories: (a) dead code — exported symbols with no callers in the tree, internal helpers used once; (b) unused imports; (c) stale comments — TODOs completed by the diff, comments describing prior behavior, doc lines that no longer match the code; (d) duplicates — near-identical helpers, repeated inline expressions that could collapse; (e) inconsistencies — naming drift, mixed patterns introduced during the window.

    For each finding give file:line, the category, one-line justification, and the proposed deletion or merge. Skip anything you're not confident about. If the window is clean, say so."

Read the full file on GitHub · 81 lines

Changes

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.

  1. 1mo ago First seen · 81 lines · 56 tokens per session scan A a59c0437531c

Subscribe to this mod's changes

rig-tidy is a skill published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 802 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

template-comprehensive-assessment

Full checkout audit for the Research Project Template — tests, architecture, docs, manuscript, pipeline. USE WHEN user asks for comprehensive assessment, full repo review, health check across projects, audit everything, or pre-merge sanity sweep for template exemplars — even without naming docs/prompts or a skill. Not…

docxology/template · 77 tokens

readiness

Use when the user wants to analyze, audit, or assess their codebase for AI agent readiness. Also use for "readiness report", "how ready is my project", "analyze my codebase", "audit my repo", "check my setup", or "what should I improve".

jrenaldi79/harness-engineering · 62 tokens

pr-sweep

Review every open PR with the code-reviewer agent and an adversarial review, apply the findings, and merge each one once CI is green. Use when asked to ship, sweep, or merge open PRs.

Chemaclass/agnostic-ai · 47 tokens

agentic-code-review

Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.

DominikTobureto/awesome-grok-build · 38 tokens

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.

DominikTobureto/awesome-grok-build · 44 tokens

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.

coco-research/coco · 38 tokens