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 agent-rig/rig --skill rig-issuegit clone --depth 1 https://github.com/agent-rig/rigWrote 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/agent-rig/rig/rig-issue)<a href="https://agentmods.dev/skills/agent-rig/rig/rig-issue"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-issue/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/agent-rig/rig/rig-issue"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-issue.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.01635 |
| Opus 5.5 | $0.00022 | $0.00654 |
| Sonnet 5.5 | $0.00011 | $0.00327 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
rig-issue 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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Manager
Manage tickets in whatever issue tracker the project is bound to. The
tracker is config-driven — read .rig/config.json first and
dispatch on tracker.provider. Never hardcode a team or project name.
Configuration
Reads .rig/config.json (missing keys → defaults):
| Key | Default | Used for |
|---|---|---|
tracker.provider |
none |
linear | github | none. Selects the backend. |
tracker.team |
— | Linear team name/key, or GitHub org, scoping list/create. |
tracker.project |
— | Linear project name for list/create. |
tracker.ticketPrefix |
— | Identifier prefix (e.g. ABC-) to recognize IDs. |
tracker.labelMapFile |
.claude/label-mapping.md |
Label source-of-truth for create. |
tracker.githubIntegration |
false |
If true, do NOT manually move states (see below). |
style.guideFile |
.claude/STYLE.md |
Writing style for the ticket title and body. |
If tracker.provider is none: this skill can't run. Explain that
ticket management needs a tracker, and point the user at
.rig/config.json → set tracker.provider to linear or github
(with team/project). Stop there.
Arguments
The user invoked this with: $ARGUMENTS
Actions
Parse the user's request as one of the actions below. Each action lists
the Linear and GitHub form — use the one matching tracker.provider.
board or list (default if no args)
- Linear:
mcp__claude_ai_Linear__list_issueswithproject=tracker.project,team=tracker.team,limit: 100. - GitHub:
gh issue list --limit 100 --json number,title,state,labels(add--repo <org/repo>fromproject.repoif not in-repo).- If
tracker.boardis configured, prefer the tracker adapter so you get the real board columns (Status), whichgh issue listcan't see: run<TRACKER> select --limit 100(and--status <col>/--dispatchableto filter), where<TRACKER>=.rig/rig-trackerif executable else<RIG_DIR>/scripts/rig-tracker.sh. It returns{number,title,url,status,labels,…}JSON. Seedocs/tracker-adapter.md.
- If
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.
- 1mo ago First seen · 140 lines · 55 tokens per session scan A 927c6b94c2e8
rig-issue is a skill published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,635 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-08-31.
Other skills, from other repositories
documentation
Use when the user asks to install or maintain a documentation index, keep CLAUDE.md or AGENTS.md inventories synchronized with files, add document metadata, classify documentation, or apply documentation-only setup to a repository.
infrastructure-project
Skill for the project management infrastructure module providing multi-project discovery, structure validation, and metadata extraction. Use when discovering active projects, validating project directory structure, or extracting project configuration metadata.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
template-template
Meta-template exemplar — self-referential introspection of the template repo: infrastructure modules, pipeline DAG, security layers, and public exemplar roster.
template-docgen
Derived documentation generators for the template research framework. Scripts that write to docs/generated/ and update in-place doc blocks.
spec-migration
Decide whether a change to the spec format needs a migration, and write it so agnostic-ai migrate rewrites old specs safely. Use when a change renames, replaces, deprecates, removes, or tightens any field users write under .agnostic-ai/ or in agnostic-ai.yaml.