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-epicnpx skills add agent-rig/rig --skill rig-epicgit 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.00118 | $0.05843 |
| Opus 5 | $0.00059 | $0.02922 |
| Sonnet 5 | $0.00024 | $0.01169 |
| Haiku 4.5 | $0.00012 | $0.00584 |
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 2d 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 — 379 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 state file (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 childfeatureissues. OmitshapeLabelsto skip.tracker.board— GitHub Projects v2 identity. When set, the parent's board transitions and each child's Done move go through therig-trackeradapter (gh issue editcan't touch a ProjectV2 Status field). Resolver used below:<TRACKER>=.rig/rig-trackerif executable else<RIG_DIR>/scripts/rig-tracker.sh(seedocs/tracker-adapter.md). Absent → skip the board moves; thelinear/nonepaths are unchanged.vcs.baseRef(origin/main),vcs.defaultBranch(main),vcs.protectedBranchMergeQueue(false).sourceScope[0]— where to explore duringplan.agents.architect/agents.reviewer(defaultrig-<role>) — for the fresh-contextreviewpanel.style.guideFile(.claude/STYLE.md) — how parent/child ticket bodies, thefinishPR 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 state file (replaces any external memory)
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.
- 2d ago First seen · 379 lines · 118 tokens per session scan A 772136dbbd40
rig-epic is a skill published in the GitHub repository agent-rig/rig (2 stars, last pushed 15d ago), licensed MIT. It adds 118 tokens to every session and 5,843 once invoked, about $0.0006 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
audit-onboarding-proposal
Independently audit a brownfield onboarding transcript, operational map, or exact proposed documentation patch before application. Use when a fresh reviewer must verify an $onboard-repository first pass, distinguish environment-caused Unknowns from reasoning defects, score its safety and evidence gates, or run a…
engineering-wisdom
Provide an explicitly requested, repository-grounded engineering review using contextual heuristics for code clarity, SOLID and design, testing, refactoring, architecture, and professional practice. Use only when the user invokes $engineering-wisdom or explicitly asks for this installed engineering-wisdom pack; do not…
red-team-adversarial
Adversarial security and resilience analysis — auto-triggered during /review and /test based on task classification. Provides attack surface analysis, boundary testing, auth bypass attempts, dependency chain attacks, and Beast Mode stress testing.
product-decision-agent
中文产品决策 Agent。用于中国大陆互联网产品、运营、增长、商业化、数据、项目推进和组织协作场景：产品规划、需求分析、PRD、需求优先级、排期、版本规划、Roadmap、MVP、灰度、上线、迭代、增长停滞、拉新、投放、渠道、裂变、CAC、LTV、ROI、留存、转化、DAU/MAU、GMV、漏斗、社区运营、内容供给、创作者、用户运营、活动运营、私域、会员、定价、指标异常、数据口径、埋点、A/B…
marketing-copy
Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.