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-ci-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-ci-setup)<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-ci-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-ci-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-ci-setup"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-ci-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.00055 | $0.02301 |
| Opus 5.5 | $0.00022 | $0.00920 |
| Sonnet 5.5 | $0.00011 | $0.00460 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
rigor-ci-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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rigor CI Setup
Wire Rigor into a project's CI so type diagnostics appear inline on the
pull / merge request, not just in the job log. This skill is the
workflow — detect the platform, choose the surface, apply the matching
template, pin, gate, verify. It does not copy the CI YAML inline: the
authoritative, version-matched templates live in the manual's CI chapter
(rigor docs ci) and as ready-to-copy files, so this skill cannot drift
out of date as --format surfaces and action versions move.
This is for users running Rigor on their own project with the
published rigor executable — Rigor is a tool, not a library, so it is
not added to the project's Gemfile.
First: load the version-current copy
Follow the copy that ships with the installed Rigor, not any vendored or frozen copy of this file. Two version-matched sources, both offline once Rigor is installed:
rigor skill --full rigor-ci-setup # this skill's current workflow, in one call
rigor docs ci # the manual's CI chapter — the actual templates
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.
The one hard rule: Rigor gets its own job
Rigor runs on Ruby 4.0. ruby/setup-ruby sets the job's active Ruby,
so a job that provisions the project's test Ruby (often 3.x, or a matrix)
cannot also provision Rigor's 4.0 — the second setup-ruby clobbers the
first. Always give Rigor a separate job (better: a separate workflow
file, for its own triggers, concurrency, and status badge). Every template
in rigor docs ci does this.
Phase 0 — Detect the project's CI platform
Inspect the repository first; do not ask what you can detect. Look for these markers from the project root and let them drive the platform choice:
| Marker (check existence) | Platform |
|---|---|
.github/workflows/ directory exists |
GitHub Actions |
.gitlab-ci.yml exists |
GitLab CI |
.circleci/config.yml exists |
CircleCI (generic recipe, junit) |
Jenkinsfile exists |
Jenkins (generic recipe, junit / checkstyle) |
bitbucket-pipelines.yml / azure-pipelines.yml / .drone.yml |
that platform (generic recipe) |
| none of the above | no CI yet — ask the user which platform they use |
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 · 173 lines · 55 tokens per session scan A 0f2996a1ca40
rigor-ci-setup is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 55 tokens to every session and 2,301 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-ci-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rigor-ci-setuprigortype/rigor | Skill | 107 | today | MPL-2.0 | A | 55 | Claude Code, Codex |
| repair-github-ciTracer-Cloud/opensre | Skill | 13k | today | Apache-2.0 | A | 40 | Claude Code, Codex |
| mcore-create-issueNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 26 | Claude Code |
| debug-taskmoonrepo/moon | Skill | 4.2k | yesterday | MIT | A | 203 | Claude Code |
| operating-github-ci-fixerTracer-Cloud/opensre | Skill | 13k | today | Apache-2.0 | A | 48 | Claude Code, Codex |
| meta-long-running-build-watchdogopensquilla/opensquilla | Skill | 7.1k | 6d ago | Apache-2.0 | A | 131 | Claude Code |
| analyze-cibenchflow-ai/skillsbench | Skill | 1.9k | 2d ago | Apache-2.0 | A | 15 | Claude Code |