What is rigor-protection-uplift?

A workflow for adding type information where Rigor's protection report finds gaps, using generated signatures first and small annotations only when needed. It also checks that no new diagnostics appear.

It is for closing protection-coverage gaps in a project that already uses Rigor, especially after reviewing its protection or mutation report.

It helps increase the bugs Rigor can catch without making working code produce new warnings.

rigor-protection-uplift — Skill for Claude Code and Codex by rigortype

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-protection-uplift

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-protection-uplift/github.svg)](https://agentmods.dev/skills/rigortype/rigor/rigor-protection-uplift)

Your own site

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

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

When invoked 1,522 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.00064	$0.01522
Opus 5.5	$0.00026	$0.00609
Sonnet 5.5	$0.00013	$0.00304
Haiku 4.5	$0.00006	$0.00152

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

Security

Grade A, and why

rigor-protection-uplift 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-protection-uplift/SKILL.md · 147 lines

How it starts

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

Rigor Protection Uplift

rigor coverage --protection (Tier 1) and rigor coverage --protection --mutation (Tier 2) surface "add a type here" — they never author the type. This skill acts on that surfacing under the discipline that keeps Rigor false-positive-safe: protection goes up, and not one line of working code starts reporting a new diagnostic.

First: load the version-current copy

This skill's exact commands, flags, carrier syntax, and rule ids 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-protection-uplift

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 user wants to raise how much of their code Rigor can actually catch bugs in.
You have coverage --protection output (an "add a type here" list) and want to close it.

When NOT to use

"Make my code more precise" with no protection goal — that is rigor coverage (precision), not --protection.
A project with no Rigor config yet — onboard first with rigor-project-init.

Load-bearing rules (read before touching a single type)

The signal prioritises and verifies; the contract sources the type. Never write the type the coverage/mutation signal "wants". Write the type the code actually has, derived from the implementation and its callers. A type guessed from the signal is a false-confidence type — worse than no type.
sig-gen first. A hand-written annotation is only the residual rigor sig-gen cannot reach. Every residual is a sig-gen-improvement to report, not just a private fix.
"Minimal" = annotation footprint, not minimal-to-kill-the-mutant. Optimising literally for mutant death games the metric. Add the smallest true annotation that models the contract; if that also kills the mutant, good.
Robustness (ADR-5). Tighten returns, keep parameters lenient. An over-tight param annotation breaks callers and breaches the false-positive discipline.

Read the full file on GitHub · 147 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 · 147 lines · 64 tokens per session scan A ef09f88f244a

Subscribe to this mod's changes

rigor-protection-uplift is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 64 tokens to every session and 1,522 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.

Debugging

rigor-protection-uplift next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rigor-protection-upliftrigortype/rigor	Skill	107	today	MPL-2.0	A	64	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
triaging-web-analytics-supportPostHog/posthog	Skill	41k	today	none	A	151	Claude Code, Codex