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 agentmods add skills/agent-rig/rig/rig-issuenpx skills add agent-rig/rig --skill rig-issuegit clone --depth 1 https://github.com/agent-rig/rigWhat 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 | $0.00055 | $0.01635 |
| Opus 5 | $0.00028 | $0.00817 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 140 lines · 55 tokens per session scan A 927c6b94c2e8
rig-issue is a skill published in the GitHub repository agent-rig/rig (2 stars, last pushed 14d ago), licensed MIT. It adds 55 tokens to every session and 1,635 once invoked, about $0.0003 per session on Opus 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
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.
administrative-services-manager
Use when a task needs the judgment of an Administrative Services Manager — evaluating a vendor contract on total cost of ownership rather than price, right-sizing a facilities/admin budget against actual utilization, anticipating where an operational process breaks at the org's next size milestone, or diagnosing why…
architectural-engineering-manager
Use when a task needs the judgment of an Architecture/Engineering firm or department manager — pricing a project fee (lump sum vs. hourly vs. % of construction cost), staffing a project against backlog, evaluating scope creep on a fixed-fee job, managing professional liability exposure, or deciding whether to pursue a…
archivist
Use when a task needs the judgment of an archivist — appraising whether a donated or transferred collection has enduring value, deciding a processing level for a backlog, writing a finding aid, triaging preservation under budget constraints, or resolving a records-restriction question.
deep-research-sprint
Orchestrates the full research sprint: fetch-before-act source warming, Research Scout → Synthesizer → Reviewer → Archivist → Orchestrator commit pipeline. USE FOR: starting a research topic with a formal synthesis deliverable; coordinating the research fleet end-to-end; producing D4 docs/research/.md files with YAML…
prompt-archaeology
Defines the prompt archaeology ritual: systematically mining prior session scratchpads, commit messages, and issue comments to surface decision rationale, failed approaches, and discovered constraints that should be encoded into the substrate. USE FOR: post-sprint review of older session artifacts (.tmp/ scratchpads…