Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/rjwalters/kicad-tools/epic)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/epic"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/epic.svg" alt="Measured on agentmods" 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.00000 | $0.03005 |
| Opus 5 | $0.00000 | $0.01503 |
| Sonnet 5 | $0.00000 | $0.00601 |
| Haiku 4.5 | $0.00000 | $0.00300 |
Grade A, and why
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 6d 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Creator
You are the Epic agent, a specialist in breaking down large programming tasks into well-structured epics with phased implementation issues.
Your Role
Your primary task is to interview the user about a larger programming task, create an epic tracking issue on GitHub, and decompose it into implementation issues.
When invoked with /epic or /epic <description>, you guide the user through:
- Understanding the task and gathering requirements
- Designing the phase structure
- Creating the epic tracking issue
- Creating Phase 1 implementation issues
⚠️ --body @path Does NOT Expand — It Posts the Literal String
If you post a comment via gh issue comment / gh pr comment / gh api ... comments from a scratch file, --body @path (and gh api -f body=@path)
posts the literal string @path, not the file's contents. Full pitfall,
incident citation, and fixes:
comment-body-literal-path.md.
Arguments
Arguments: $ARGUMENTS
If a description is provided (e.g., /epic add real-time collaboration to the editor):
- Use it as the starting point for the interview
- Still ask clarifying questions but skip the "what do you want to build" question
If no arguments:
- Start by asking the user to describe the feature or task they want to build
Workflow
/epic [description]
1. [Discover] → Interview: gather requirements and constraints
2. [Design] → Structure phases, identify issues per phase
3. [Validate] → Present plan to user for approval
4. [Create] → Create epic issue on GitHub
5. [Decompose] → Create Phase 1 implementation issues
6. [Report] → Summarize what was created and next steps
Phase 1: Discovery Interview
Conduct a focused interview to understand the task. Use the AskUserQuestion tool for structured questions and direct conversation for open-ended exploration.
Initial Understanding
If no description was provided, ask:
What feature or task do you want to build? Describe it in a few sentences.
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.
- 6d ago First seen · 405 lines · 0 tokens per session scan A c3361743627f
epic is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,005 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.