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.
git clone --depth 1 https://github.com/vinnie357/claude-skillsWrote 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/commands/vinnie357/claude-skills/plan-epic)<a href="https://agentmods.dev/commands/vinnie357/claude-skills/plan-epic"><img src="https://agentmods.dev/badge/commands/vinnie357/claude-skills/plan-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.
<a href="https://agentmods.dev/commands/vinnie357/claude-skills/plan-epic"><img src="https://agentmods.dev/badge/commands/vinnie357/claude-skills/plan-epic.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.00015 | $0.01107 |
| Opus 5 | $0.00008 | $0.00553 |
| Sonnet 5 | $0.00003 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
plan-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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a new VantageEx-compatible epic in Linear.
Steps
- Load the
/linearskill - Read the epic template at
templates/0.1.0/epic.md - Read the epic format spec at
references/epic-format.md
Gather Information
Interactively collect from the user:
- Title: Clear, imperative statement of what gets built
- Slug: Derive from title (kebab-case, max ~30 chars). Confirm with user.
- Objective: 2-3 sentences defining success criteria
- Skills: Domain-specific skills needed. Validate each against the marketplace at
https://github.com/vinnie357/claude-skills/blob/main/.claude-plugin/marketplace.json. Warn if a skill is not found. - Repos: Target repositories
- Constraints: Optional. Note that defaults apply (mise run ci, no attribution, squash merge, feature/)
- Team: Optional. Default: lead=sonnet, default_model=haiku, escalation=haiku->sonnet->opus
Size & Order
Apply references/epic-sizing.md to the issues you intend to create:
- Decompose the epic into 3–8 independently completable issues. If the count would exceed 8, split the epic.
- Size each issue to one worker session: ≤ ~10 target files, one deliverable, one subsystem, verifiable by a single acceptance check. Reject multi-deliverable titles (joined by "and/also/then/plus") — split them.
- Declare dependencies explicitly using Linear blocking relations. Never rely on implicit ordering.
- Order topologically: foundation issues (schemas, references, interfaces) first, then core, integration, and verification. No cycles — if a cycle is detected, re-decompose before proceeding.
- Keep chains shallow: dependency depth < 5 levels; do not serialize issues that can run in parallel.
See references/epic-sizing.md for thresholds and the full checklist.
Validate
Before creating:
- Confirm skills exist in the marketplace (read marketplace.json from the claude-skills repo)
- Confirm core skills are NOT listed (anti-fabrication, git, tdd, twelve-factor, security, mise, nushell)
- Confirm objective is 2-3 sentences
- Confirm slug is kebab-case and under 30 chars
- Confirm at least one repo is specified
- Confirm the body is self-contained: no local-filesystem paths (
~/.claude/...,/Users/<name>/...) used as the source of truth. Embed design plans inline under a## Design contextsection, or link to other epics by Linear URL. - Sizing check: confirm the objective's scope can decompose into approximately 6–8 independently-shippable issues (the adopted sizing convention; see "Epic Sizing Heuristics" in
references/epic-format.md). If the scope appears to require significantly more issues, spans many repositories with large cross-cutting changes, or contains work that could be separately delivered, prompt the user to consider splitting into multiple epics. - Dependency-ordering check: confirm that the anticipated issues can be ordered topologically (foundational work first, no cycles). If the user has described ordering intent, include a
## Dependenciessection in the epic body; see "Dependency Ordering" inreferences/epic-format.mdfor format and rules.
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.
- 5d ago First seen · 80 lines · 15 tokens per session scan A 9631bf4e3312
plan-epic is a command published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 1,107 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.