A question-answering workflow for Rigor based on the installed tool's bundled documentation and analysis of the user's code. Rigor is a static-analysis tool that examines code for type and other programming problems.

Use it to explain diagnostics, types, configuration, flags, framework support, method typing, inferred types, or comparisons with other type checkers.

It avoids answers based on outdated documentation or general guesses when command behavior and diagnostics can vary by installed version.

rigor-ask — Skill for Claude Code and Codex by rigortype/rigor

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-ask

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.

README.md

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

Your own site

<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-ask"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-ask/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-ask"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-ask.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,052 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.00063	$0.03052
Opus 5.5	$0.00025	$0.01221
Sonnet 5.5	$0.00013	$0.00610
Haiku 4.5	$0.00006	$0.00305

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

Security

Grade A, and why

rigor-ask 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-ask/SKILL.md · 198 lines

How it starts

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

Ask Rigor anything

Someone has a question about Rigor. It might be about a diagnostic, the type model, a flag, how Rigor stacks up against another type checker, whether Rigor can handle their framework, how to type a method — or just "what is this, and should I use it?" Whatever it is, answer from the source, not from memory.

Two things make that easy, and you have both offline:

Rigor's own docs ship inside the gem. rigor docs serves the full handbook and manual, always matching the user's installed version, no network. This is the authoritative copy: a rule's exact firing condition, a flag's spelling, a config default — all drift release to release, and rigor docs is the copy that shipped with this install, so an answer drawn from it cannot disagree with the binary they run.
Rigor can read the user's actual code. When the question is about their program — "why is this flagged?", "what type does Rigor see here?", "how well-typed is my project?" — rigor check / annotate / type-of / triage / coverage answer from what Rigor inferred. A concrete inferred type beats any abstract explanation.

This is the user's shortcut: they only ever need to remember three skills — rigor-next-steps ("what should we do next?"), rigor-ask ("answer this about Rigor"), and rigor-type-oracle ("before you write a type, ask Rigor"). They ask in plain language; you turn it into the right lookup or analysis so they never have to remember the command.

Prefer the live map over this skill's tables

The doc-page names and command flags below are a snapshot; Rigor's pages and CLI move release to release, and a vendored copy of this skill (e.g. added via npx skills) lags further still. Treat the tables as orientation, then confirm against the installed Rigor, which is always current:

rigor docs --list              # the live doc map — what pages exist in THIS version
rigor --help                   # the live command + flag list
rigor skill --full rigor-ask   # the current version of this skill itself

Read the full file on GitHub · 198 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.

11d ago First seen · 198 lines · 63 tokens per session scan A 7037b80de3bb

Subscribe to this mod's changes

rigor-ask is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 63 tokens to every session and 3,052 once invoked, about $0.0003 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.

Learning and teaching Research

rigor-ask next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rigor-askrigortype/rigor	Skill	107	today	MPL-2.0	A	63	Claude Code, Codex
hr-onboardingnexu-io/open-design	Skill	106k	today	Apache-2.0	A	62	Claude Code, Codex
book-mirrorgarrytan/gbrain	Skill	32k	today	MIT	A	138	Claude Code
exam-forecastanthropics/claude-for-legal	Skill	9.9k	3d ago	Apache-2.0	A	73	Claude Code
lean-formalizewanshuiyin/Auto-claude-code-research-in-sleep	Skill	19k	3d ago	MIT	A	81	Claude Code
eli5companion-inc/feynman	Skill	10k	6d ago	MIT	A	63	Claude Code, Codex
deck-course-modulenexu-io/html-anything	Skill	9.4k	24d ago	Apache-2.0	A	25	Claude Code, Codex