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-sprintgit 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-sprint)<a href="https://agentmods.dev/skills/agent-rig/rig/rig-sprint"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-sprint/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-sprint"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-sprint.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.00133 | $0.02423 |
| Opus 5.5 | $0.00053 | $0.00969 |
| Sonnet 5.5 | $0.00027 | $0.00485 |
| Haiku 4.5 | $0.00013 | $0.00242 |
Grade A, and why
rig-sprint 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Orchestrator
A sprint is a batch of independent work items that each land on the trunk on their own. Use this when the work decomposes into pieces that don't interleave (no shared runtime contract across siblings, no half-migrated state if you ship one without the others). If children do interleave, use an epic / integration-branch flow instead — same decomposition step, plus a shared branch the children stack on.
Configuration
Reads .rig/config.json (missing keys → defaults):
| Key | Default | Used for |
|---|---|---|
tracker.provider |
none |
linear | github | none. Selects the ticket backend, or ad-hoc mode. |
tracker.team |
— | Linear team / GitHub org for list/create. |
tracker.project |
— | Linear project for list/create. |
tracker.ticketPrefix |
— | Recognize ticket IDs in $ARGUMENTS. |
tracker.githubIntegration |
false |
If true, GitHub drives PR/merge transitions; each /rig-task sets only the start-of-work In Progress. |
tracker.shapeLabels.sprint |
sprint |
GitHub-only label applied to each item at creation so a board/dispatcher can pick up sprint items. Omit shapeLabels to skip. |
vcs.baseRef |
origin/main |
Base each ticket's branch is cut from. |
vcs.branchConvention |
{user}/{ticket}-{slug} |
New-branch template. |
vcs.defaultBranch |
main |
Trunk each PR targets. |
vcs.protectedBranchMergeQueue |
false |
If true, merge via gh pr merge --auto and never pass --rebase/--squash. |
runtime.installCommand / packageManager |
npm |
Install command inside a worktree. |
test.command |
npm test |
Test step in each per-ticket implementation. |
sourceScope[0] |
src |
Default codebase area to explore during decomposition. |
style.guideFile |
.claude/STYLE.md |
Writing style for item titles, bodies, and the hand-off report. |
Tracker modes:
linear— tickets are Linear issues; use themcp__claude_ai_Linear__*tools.github— tickets are GitHub issues; usegh issue.none— ad-hoc mode. There are no ticket IDs. Treat each item in$ARGUMENTS(or each bullet the user gives) as a task description. Skip all create/list/move-ticket steps; the sprint operates directly on the task list, and each task's implementation opens a PR whose title is the task description.plan <feature>still decomposes into a numbered task list — it just prints it instead of creating tickets.
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 · 165 lines · 133 tokens per session scan A c8c0c711ceee
rig-sprint is a skill published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 2,423 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-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.