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-mcp-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-mcp-setup)<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-mcp-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-mcp-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-mcp-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-mcp-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.00057 | $0.01360 |
| Opus 5.5 | $0.00023 | $0.00544 |
| Sonnet 5.5 | $0.00011 | $0.00272 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
rigor-mcp-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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rigor MCP Setup
rigor mcp is the Model Context Protocol server bundled with the
rigortype gem. It exposes Rigor's analysis as JSON-RPC tool calls over
stdio, so an AI coding agent can call Rigor directly during a session —
check types before a refactor, look up the type at a cursor, or triage a
project's diagnostics as review context. All tools are read-only
(write-side commands like rigor init / sig-gen --write are
deliberately excluded — modifying files stays the developer's call).
The authoritative, per-client configuration lives in the manual. With Rigor installed, read it offline with no network round-trip:
rigor docs mcp-server
(Web fallback, only before Rigor is installed: Rigor MCP Server — AI Agent Integration.) This skill is the workflow around it (identify the client → apply the manual's snippet → verify the handshake), so it does not duplicate (and cannot stale-out) the config details.
First: load the version-current copy
The config details already come live from rigor docs; this keeps the
workflow itself current too. Prefer the copy of this skill that ships
with the installed Rigor over any vendored or frozen copy of this file:
rigor skill --full rigor-mcp-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
- A developer wants their AI agent to call Rigor's tools mid-session.
- A project commits a shared MCP config (
.mcp.json,.cursor/mcp.json) and you want to add Rigor to it for the whole team.
When NOT to use
- Editor (human) integration — that is
rigor-editor-setup(rigor lsp). - The project has no Rigor config yet — run
rigor-project-initfirst (the MCP tools use the same.rigor.ymldiscovery asrigor check).
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 · 133 lines · 57 tokens per session scan A f52b292ff49e
rigor-mcp-setup is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 57 tokens to every session and 1,360 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-mcp-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rigor-mcp-setuprigortype/rigor | Skill | 107 | today | MPL-2.0 | A | 57 | 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 |