agentmods.dev

rigor-plugin-tune

rigor-plugin-tune is a skill for Claude Code, Codex from rigortype/rigor. It costs 55 tokens per session (874 once invoked), scanned A, original, MPL-2.0.

A workflow for matching a Ruby project's Gemfile.lock—the record of its installed gems—to Rigor's bundled plugins, then enabling the plugins needed by those gems.

In plain words
What is it for?
It is for updating plugin settings after adding or removing gems, or when Rigor lacks understanding of a dependency.
Why use it?
It prevents Rigor from missing framework or library knowledge after dependencies change.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 107repo today A scan 55 tokens original MPL-2.0

Good fit It is for updating plugin settings after adding or removing gems, or when Rigor lacks understanding of a dependency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rigortype/rigor/rigor-plugin-tune
View source ↗ rigortype/rigor rigor.typedduck.fail
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 rigortype/rigor --skill rigor-plugin-tune
Clone the repo
git clone --depth 1 https://github.com/rigortype/rigor

Made for: Claude Code, Codex.

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 rigor-plugin-tune

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-plugin-tune"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-plugin-tune.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 874 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.00055 $0.00874
Opus 5.5 $0.00022 $0.00350
Sonnet 5.5 $0.00011 $0.00175
Haiku 4.5 $0.00006 $0.00087

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

Security

Grade A, and why

rigor-plugin-tune 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 11d 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/rigor-plugin-tune/SKILL.md · 101 lines

How it starts

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

Rigor Plugin Tune

rigor-project-init selects plugins once, at onboarding. Dependencies drift afterward — a project adds Sidekiq, adopts dry-rb, brings in shoulda-matchers — and the bundled Rigor plugin that understands the new gem is not enabled until someone wires it. This skill is the recurring "re-match plugins to the current Gemfile.lock" pass.

All rigor-* plugins ship bundled inside the rigortype gem — no separate install. Enabling one is just adding its id to plugins: in .rigor.dist.yml.

First: load the version-current copy

This skill's exact commands, flags, and config keys drift between Rigor releases, so follow the copy that ships with the installed Rigor rather than any vendored or frozen copy of this file. Get the complete current procedure in one call:

rigor skill --full rigor-plugin-tune

If you already loaded this skill via rigor skill you have the current copy — just proceed. If rigor is not on PATH, this task needs it: run rigor-next-steps to install Rigor first, then come back.

When to use

  • The project added (or removed) a gem since it was onboarded.
  • rigor check is missing framework knowledge (e.g. ActiveRecord relation methods, RSpec matchers) that a bundled plugin would supply.

When NOT to use

  • First-time setup — rigor-project-init does the initial selection.
  • A gem with no bundled plugin and no RBS — that is rigor-rbs-setup (community RBS) or, for your own DSL, rigor-plugin-author.

Procedure

Phase 1 — list what is enabled vs what is installed

Read the current plugins: in .rigor.dist.yml, and the project's dependencies in Gemfile.lock.

Phase 2 — match against the bundled catalogue

The authoritative, current list of bundled plugins (the count drifts as new ones land) comes from the installed Rigor itself — read it there, not from a web page that may describe a different version:

rigor docs manual/plugins/README   # the catalogue of every bundled plugin, offline
rigor plugins                      # what is enabled in THIS project right now

Read the full file on GitHub · 101 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. 11d ago First seen · 101 lines · 55 tokens per session scan A ba702be9e496

Subscribe to this mod's changes

rigor-plugin-tune is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 55 tokens to every session and 874 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-10-26.

Debugging
Related

rigor-plugin-tune compared with skills from other repositories

rigor-plugin-tune next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
rigor-plugin-tunerigortype/rigorSkill107todayMPL-2.0A55Claude Code, Codex
systematic-debuggingopen-metadata/OpenMetadataSkill16kyesterdayApache-2.0A37Claude Code
log-error-digestzebbern/claude-code-guideSkill4.7k3d agoMITA71Claude Code, Codex
cwv-optimizeradobe/skillsSkill319yesterdayApache-2.0A112Claude Code
ci-fixersipyourdrink-ltd/bernsteinSkill1.2kyesterdayApache-2.0A15Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skillsSkill1.9k23d agoMITA36Claude Code
diagnosing-missing-recordingsPostHog/posthogSkill41ktodaynoneA76Claude Code, Codex