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 rigortype/rigor --skill rigor-rbs-setupgit clone --depth 1 https://github.com/rigortype/rigorWrote 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/rigortype/rigor/rigor-rbs-setup)<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-rbs-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-rbs-setup/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/rigortype/rigor/rigor-rbs-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-rbs-setup.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.00060 | $0.01279 |
| Opus 5.5 | $0.00024 | $0.00512 |
| Sonnet 5.5 | $0.00012 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
rigor-rbs-setup 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rigor RBS Setup
Most of what Rigor cannot type on a real application is the surface of
third-party gems that ship no RBS: a call into such a gem returns
Dynamic, so every downstream method on the result is unprotected and
some genuine bugs go uncaught. The Ruby ecosystem's answer is the
community RBS collection at
ruby/gem_rbs_collection;
this skill wires it into the project.
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-rbs-setup
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
rigor checkends withinfo: N gem(s) in Gemfile.lock have no RBS available: …— that list is the gap this skill closes.- A deep call chain into a gem (an HTTP client, a parser, a service
object) types as
Dynamicand you want Rigor to see through it.
When NOT to use
- The project has no Rigor config yet — run
rigor-project-initfirst. - A specific gem you need is not in the community collection — RBS
setup will not cover it. That residue is for
rigor-plugin-author(if it is your own DSL) or a Rigor issue (if it is a popular gem worth built-in support).
How Rigor consumes it (so you know what "done" looks like)
Rigor auto-detects rbs_collection.lock.yaml at the project root
(rbs_collection.auto_detect defaults to true) and feeds each gem's
downloaded RBS directory into its signature paths, skipping stdlib
entries it already bundles. No .rigor.yml change is required — the
lockfile's presence is the whole wiring. (Set rbs_collection.lockfile:
only if the lockfile lives somewhere other than the project root.)
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 · 146 lines · 60 tokens per session scan A c9cabd08c45d
rigor-rbs-setup is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 60 tokens to every session and 1,279 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.
rigor-rbs-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rigor-rbs-setuprigortype/rigor | Skill | 107 | today | MPL-2.0 | A | 60 | Claude Code, Codex |
| sentry-ruby-sdkgetsentry/sentry-for-ai | Skill | 275 | yesterday | MIT | A | 98 | Claude Code |
| error-tracking-rubyPostHog/skills | Skill | 79 | yesterday | MIT | A | 13 | Claude Code |
| sentry-ruby-sdkis-bo/fullstack-forge-skill | Skill | 2 | 6d ago | Apache-2.0 | A | 98 | Claude Code |
| Upgrade Fixdhruvasagar/ruby-upgrade-toolkit | Skill | 14 | 6mo ago | none | A | 101 | Claude Code |
| Upgrade Auditdhruvasagar/ruby-upgrade-toolkit | Skill | 14 | 6mo ago | none | A | 63 | Claude Code |
| debug:railsSnakeO/claude-debug-and-refactor-skills-plugin | Skill | 9 | 9mo ago | none | A | 61 | Claude Code |