rig-epic

rig-epic is a skill for Claude Code from agent-rig/rig. It costs 118 tokens per session (6,592 once invoked), scanned A, original, MIT.

A workflow guide for delivering a large feature made up of several related work items. It organises a parent task and smaller child tasks on a shared integration branch, a temporary branch where dependent changes are combined before reaching the main code line.

In plain words
What is it for?
Use it to plan multi-ticket features whose parts must be developed together. It can create and track parent and child items through Linear, GitHub, or a local state file, depending on project settings.
Why use it?
It keeps the main code line from being temporarily broken when one child task depends on another unfinished task. Each child change can still be reviewed separately before the whole feature is combined.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Good fit Use it to plan multi-ticket features whose parts must be developed together. It can create and track parent and child items through Linear, GitHub, or a local state file, depending on project settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agent-rig/rig/rig-epic
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 agent-rig/rig --skill rig-epic
Clone the repo
git clone --depth 1 https://github.com/agent-rig/rig

Made for: Claude Code.

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 rig-epic

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-rig/rig/rig-epic"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-epic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,592 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.00118 $0.06592
Opus 5.5 $0.00047 $0.02637
Sonnet 5.5 $0.00024 $0.01318
Haiku 4.5 $0.00012 $0.00659

Measured 1mo ago against content hash cc0981451d3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rig-epic 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.

skills/rig-epic/SKILL.md · 420 lines

How it starts

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

rig-epic — integration-branch workflow

For multi-item arcs where landing each item directly on the trunk would temporarily break the runtime contract, stack child PRs on a shared integration branch and squash that branch into the trunk as one PR at the end. Each child PR is reviewed as the step it actually is; the trunk-bound delivery is one squashed rebase.

Configuration

Reads .rig/config.json (defaults in parentheses):

  • tracker.provider — linear | github | none (none). How parent/child items are stored. none → items live only in the epic run state (below); no tracker calls.
  • tracker.team / tracker.project / tracker.ticketPrefix / tracker.githubIntegration.
  • tracker.shapeLabels.epic (epic) — GitHub-only label put on the parent at creation so a Project board / dispatcher can distinguish the epic from child feature issues. Omit shapeLabels to skip.
  • tracker.board — GitHub Projects v2 identity. When set, the parent's board transitions and each child's Done move go through the rig-tracker adapter (gh issue edit can't touch a ProjectV2 Status field). Resolver used below: <TRACKER> = .rig/rig-tracker if executable else <RIG_DIR>/scripts/rig-tracker.sh (see docs/tracker-adapter.md). Absent → skip the board moves; the linear/none paths are unchanged.
  • vcs.baseRef (origin/main), vcs.defaultBranch (main), vcs.protectedBranchMergeQueue (false).
  • sourceScope[0] — where to explore during plan.
  • agents.architect / agents.reviewer (default rig-<role>) — for the fresh-context review panel.
  • style.guideFile (.claude/STYLE.md) — how parent/child ticket bodies, the finish PR body, and every status report are written.

Delegates to /rig-task (per child), /rig-worktree (checkouts), /rig-review

  • /rig-review fix (the combined-diff review), /rig-tidy (optional).

Epic run state (replaces any external memory)

Read the full file on GitHub · 420 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. 1mo ago Changed · +41 lines cc0981451d3d
  2. 1mo ago First seen · 379 lines · 118 tokens per session scan A 772136dbbd40

Subscribe to this mod's changes

rig-epic is a skill published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 6,592 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.

Related

Other skills, from other repositories

agnostic-ai-gh-issues

Work the open issues that are unassigned or assigned to you, one at a time through agnostic-ai-gh-issue. Use when asked to work the backlog.

Chemaclass/agnostic-ai · 40 tokens

pmstudio-changelog

Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records.…

coco-research/coco · 98 tokens

gsd-quick

Use when the user wants a small, ad-hoc change handled with GSD guarantees (atomic commits, STATE.md) but without the full pipeline. Tasks land in .planning/quick/; --full, --discuss, --research, --validate add the skipped agents back.

coco-research/coco · 62 tokens

bds-workflow

10-step beads-starter workflow guide. Runs only on explicit invocation.

seungyeop-lee/beads-starter · 19 tokens

repository-bootstrap

Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.

cz1993/vibe-coding-repository-standard · 41 tokens

project-bootstrap

Bootstrap a new or bare repository with a sane, stack-matched baseline, then hand off to init-worktracking for work tracking. Detects the language and package manager, then lays down .gitignore, .editorconfig, a linter/formatter config, a LICENSE, and a README stub, without clobbering anything that already exists. Use…

hams-ollo/zen-agent-skills · 148 tokens