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-next-stepsgit 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-next-steps)<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-next-steps"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-next-steps/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-next-steps"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-next-steps.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.00062 | $0.01316 |
| Opus 5.5 | $0.00025 | $0.00526 |
| Sonnet 5.5 | $0.00012 | $0.00263 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
rigor-next-steps 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rigor Next Steps
The single entry point for "what should we do next with Rigor on this
project?" This skill is deliberately thin: it only does the
bootstrap that must happen before rigor can speak for itself, then it
hands the decision to the installed rigor binary via
rigor skill describe. That keeps the advice current to the
installed version — the routing intelligence lives in the gem, not
frozen in this file (ADR-73).
Work top to bottom. Stop at the first step that is not yet satisfied, complete it, then continue.
Autonomous / non-interactive runs
When the user has delegated the journey up front ("set this project up and get it healthy; don't wait for me"), the skills below still contain ask-the-user points. Handle them like this:
- A choice the user already made in their instruction (e.g. the adoption mode) is settled — record it and proceed; do not re-ask.
- A low-risk, reversible, in-repo action a skill says to confirm
(installing an RBS collection, a
.gitignoreaddition) is covered by the standing delegation — do it, and note the self-answer in your report. - Committing, pushing, or publishing is never covered by a general delegation — leave the files uncommitted and list them for the user.
- A step only a human can complete or verify (watching a CI run execute, confirming live diagnostics inside an editor) is a handoff, not a stall: do the file-level part if it is safe, then report what remains for the user instead of waiting.
Step 1 — Resolve the rigor command
rigor --version
If it prints a version (rigor 0.x.y), rigor is installed — go to
Step 3. If the command is not found, go to Step 2.
Step 2 — Install Rigor (only if Step 1 failed)
Rigor is a standalone tool, not a project dependency — do not add it
to the Gemfile. Fetch and follow the install guide, which is written
for an AI agent and picks the right channel (mise / asdf / gem / Docker)
for the environment:
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 · 137 lines · 62 tokens per session scan A 3d2f18183746
rigor-next-steps is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 62 tokens to every session and 1,316 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-next-steps compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rigor-next-stepsrigortype/rigor | Skill | 107 | today | MPL-2.0 | A | 62 | Claude Code, Codex |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | yesterday | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | 3d ago | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 319 | yesterday | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 1.9k | 23d ago | MIT | A | 36 | Claude Code |
| diagnosing-missing-recordingsPostHog/posthog | Skill | 41k | today | none | A | 76 | Claude Code, Codex |