What is rigor-plugin-author?

A procedure for creating a new Rigor add-on for a Ruby library, framework, or custom language feature. The add-on teaches Rigor how to understand that feature without changing the main analyzer.

Use it to add support for a real Ruby gem or framework, or for an in-house project language feature, choosing between production support and an example walkthrough.

It gives new support a defined home and distinguishes new add-ons from edits to existing add-ons or the analyzer itself.

How rigortype/rigor configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to rigortype/rigor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rigortype/rigor/master/.claude/skills/rigor-plugin-author/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/rigortype/rigor

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rigortype/rigor/rigor-plugin-author/github.svg)](https://agentmods.dev/skills/rigortype/rigor/rigor-plugin-author)

Your own site

<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-plugin-author"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-plugin-author/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-plugin-author"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-plugin-author.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 3,431 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.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.03431
Opus 5.5	$0.00022	$0.01372
Sonnet 5.5	$0.00011	$0.00686
Haiku 4.5	$0.00006	$0.00343

Measured 11d ago against content hash 4e63d5da78ab, 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-author 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.

.claude/skills/rigor-plugin-author/SKILL.md · 122 lines

How it starts

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

Rigor Plugin Author

Decide placement first (Phase 0 below), then load the four reference files in order. All commands run through the Nix Flake (nix develop --command ...) per AGENTS.md.

Phase 0 — Decide where the plugin lands

Trigger this skill when the user requests a new plugin: "Create a Rigor plugin that catches Y", "Extend Rigor to understand our DSL Z", "Write a plugin similar to rigor-units but for currency", or Japanese equivalents.

Do NOT trigger for:

Edits / bug-fixes / new diagnostics on an existing plugin under plugins/<id>/ or examples/<id>/ — these are ordinary edit tasks; modify the plugin in place and add a changelog.d/ fragment.
Analyser-engine work in lib/rigor/inference/ / lib/rigor/analysis/ / lib/rigor/plugin/ — that's core development.
Post-landing maintenance (refactor / rename / dependency bump on an already-shipped plugin) — these don't need the 10-phase pipeline; they're scoped per task.

Signal	Lands under
Real gem / framework (Rails, RSpec, dry-rb, Sorbet, Devise, Sidekiq, GraphQL, …)	`plugins/<id>/`
User's in-house DSL on a real project	`plugins/<id>/`
Installed via `Gemfile`, activated in `.rigor.yml` against real source	`plugins/<id>/`
Deliberately fictional / virtual domain (tiny Lisp, units-of-measure, fake route YAML)	`examples/<id>/`
Authored to demonstrate one architectural surface of the contract	`examples/<id>/`
Referenced by the handbook / ADRs as a teaching reference	`examples/<id>/`

Default to plugins/. The walkthroughs under examples/ are a curated set; adding to that tree requires a positive teaching reason.

Mechanical differences: production specs live at spec/integration/plugins/<id>_plugin_spec.rb; walkthrough specs at spec/integration/examples/<id>_plugin_spec.rb. Both auto-include spec/integration/support/plugin_helpers.rb. RuboCop excludes plugins/**/* and examples/**/* but lints the specs.

Read the full file on GitHub · 122 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

11d ago First seen · 122 lines · 55 tokens per session scan A 4e63d5da78ab

Subscribe to this mod's changes

rigor-plugin-author 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 3,431 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.

Building agents Languages Ruby

rigor-plugin-author next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rigor-plugin-authorrigortype/rigor	Skill	107	today	MPL-2.0	A	55	Claude Code
newclacky-ai/openclacky	Skill	1.2k	yesterday	MIT	A	10	Claude Code
rspec-conventionsrootstrap/rails_api_base	Skill	634	2d ago	MIT	A	82	Claude Code
dhh-rails-styledavekilleen/Dex	Skill	512	8d ago	MIT	A	115	Claude Code
ruby-patternssoftspark/ai-toolkit	Skill	179	10d ago	Apache-2.0	A	60	Claude Code
ruby-idiomsirahardianto/awesome-agv	Skill	158	23d ago	MIT	A	61	Claude Code, Codex
ruby-rulessoftspark/ai-toolkit	Skill	179	10d ago	Apache-2.0	A	48	Claude Code

rigor: Skill for Claude Code