What is rigor-queue-release?

A workflow for reducing an existing Rigor baseline, a file that records already-accepted analysis findings. It reviews findings rule by rule, fixes or intentionally suppresses them, reports issues, and regenerates the baseline.

Use it to diagnose baseline entries, fix accepted findings, record intentional suppressions, and refresh `.rigor-baseline.yml`.

It helps improve a project that already uses a baseline without treating every old finding as a new failure. It is not for first-time setup or writing plugins.

rigor-queue-release — 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-queue-release

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

Your own site

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

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

When invoked 1,904 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.00117	$0.01904
Opus 5.5	$0.00047	$0.00762
Sonnet 5.5	$0.00023	$0.00381
Haiku 4.5	$0.00012	$0.00190

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

Security

Grade A, and why

rigor-queue-release 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 today.

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.

agents/pi-harness/skills/rigor-queue-release/SKILL.md · 167 lines

How it starts

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

Rigor queue — release pre-clear

Orchestrator-led, multi-turn, in-session queue. Primary entry: user runs pi in the Rigor repo (packages in .pi/settings.json) then /queue-release or /skill:rigor-queue-release. Same project session continues with pi -c.

Not a one-shot architect→lane.

See also: ../../roles/orchestrator.md, ../../contracts/README.md (QueueTurn), project agents under .pi/agents/ (rigor-lane, rigor-reviewer).

Requires project package npm:pi-subagents (listed in .pi/settings.json).

Hard rules (always)

A release goal / milestone / vX.Y.Z wording is NOT authorization to cut a release. Never seal changelog, bump VERSION / lib/rigor/version.rb, open release/x.y.z, or run /rigor-release-prep unless the user explicitly invoked release-prep.
When the queue is clear enough, say the cut is one /rigor-release-prep away — do not start it.
Lanes: push head SHA and stop; this parent owns CI. No parallel host make verify. Issues = backlog (ADR-98).
GitHub API: sparse CI polls (gh pr view --json statusCheckRollup), ≤1/min/PR.
Never mutate release metadata in this queue.
Managed worktree fanout needs a clean source checkout (excluding .pi/subagents/ runtime state). Do not auto-merge worktree patches into master without a human.

Turn protocol (in this same session)

Every turn:

Restate queue goal + constraints (target version as context; non-authorization rule).
Show ranked backlog (open Issues) with evidence (gh issue list / gh issue view). Rank: bugs/blockers > tidy before that cut.
Propose exactly one next unit of work (unless the user asked for a parallel batch — see spawn below).
Wait for user: next / do #N / skip / stop (JA: 次 / やる #N / スキップ / 止めて / ストップ). Also accept spawn / spawn N / 全部やれ / parallel for fanout.
On go — prefer pi-subagents spawn (do not tell the user to open another terminal for run-role.sh when the package is available):

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

today Changed · +2 lines dd036f718981
11d ago First seen · 165 lines · 117 tokens per session scan A ebff05efa3b5

Subscribe to this mod's changes

rigor-queue-release is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 117 tokens to every session and 1,904 once invoked, about $0.0005 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-queue-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rigor-queue-releaserigortype/rigor	Skill	107	today	MPL-2.0	A	117	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	2d 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