rigor-editor-setup

rigor-editor-setup is a skill for Claude Code, Codex from rigortype/rigor. It costs 68 tokens per session (1,412 once invoked), scanned A, original, MPL-2.0.

A setup workflow for Rigor's language server, a background program that gives code tools to editors. It enables live diagnostics, type information on hover, an outline, and type-aware completion in supported editors.

In plain words
What is it for?
It is for connecting Rigor to VS Code, Neovim, Helix, Emacs, or another editor that supports the Language Server Protocol.
Why use it?
It brings Rigor's feedback into the editor while code is being written instead of limiting it to command-line or CI checks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for connecting Rigor to VS Code, Neovim, Helix, Emacs, or another editor that supports the Language Server Protocol.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rigortype/rigor/rigor-editor-setup
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-editor-setup
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.

agentmods badge for rigor-editor-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/rigortype/rigor/rigor-editor-setup/github.svg)](https://agentmods.dev/skills/rigortype/rigor/rigor-editor-setup)
Your own site
<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-editor-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-editor-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.

agentmods 80×15 button for rigor-editor-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-editor-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-editor-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,412 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.01412
Opus 5.5 $0.00027 $0.00565
Sonnet 5.5 $0.00014 $0.00282
Haiku 4.5 $0.00007 $0.00141

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

Security

Grade A, and why

rigor-editor-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.

skills/rigor-editor-setup/SKILL.md · 142 lines

How it starts

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

Rigor Editor Setup

rigor lsp is the in-process Language Server bundled with the rigortype gem. It speaks LSP over stdio and turns Rigor's analyzer into a live editor experience: diagnostics as you type, hover-to-type, an outline view, and type-aware completion. This skill wires it into the developer's editor.

The authoritative, per-editor configuration lives in the manual. With Rigor installed, read it offline with no network round-trip:

rigor docs editor-integration

(Web fallback, only before Rigor is installed: Rigor LSP — Editor Integration.) This skill is the workflow around it (identify the editor → apply the manual's snippet → verify), 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 section 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-editor-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 Rigor feedback live in their editor, not just from rigor check on the command line.
  • A project commits a shared editor config (e.g. .vscode/) and you want to add Rigor's LSP to it so the whole team gets it.

When NOT to use

  • Wiring Rigor into CI — that is rigor-ci-setup.
  • The project has no Rigor config yet — run rigor-project-init first (the LSP uses the same .rigor.yml discovery as rigor check).

The one stable fact

Every editor snippet simply launches rigor lsp (stdio) and needs rigor on the editor's PATH — the same executable rigor check uses. For GUI editors that do not inherit your shell, the mise shim path is the most reliable channel (see rigor docs install, or Installing Rigor on the web). Do not add rigortype to the project's Gemfile — it is a tool, not a library.

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

  1. 11d ago First seen · 142 lines · 68 tokens per session scan A 348c0a04a67d

Subscribe to this mod's changes

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

Related

rigor-editor-setup compared with skills from other repositories

rigor-editor-setup next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
rigor-editor-setuprigortype/rigorSkill107todayMPL-2.0A68Claude Code, Codex
systematic-debuggingopen-metadata/OpenMetadataSkill16kyesterdayApache-2.0A37Claude Code
log-error-digestzebbern/claude-code-guideSkill4.7k3d agoMITA71Claude Code, Codex
cwv-optimizeradobe/skillsSkill319yesterdayApache-2.0A112Claude Code
ci-fixersipyourdrink-ltd/bernsteinSkill1.2kyesterdayApache-2.0A15Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skillsSkill1.9k23d agoMITA36Claude Code
diagnosing-missing-recordingsPostHog/posthogSkill41ktodaynoneA76Claude Code, Codex