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 commands/el-feo/ai-context/create-epicsgit clone --depth 1 https://github.com/el-feo/ai-contextWhat 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.00017 | $0.03600 |
| Opus 5 | $0.00009 | $0.01800 |
| Sonnet 5 | $0.00003 | $0.00720 |
| Haiku 4.5 | $0.00002 | $0.00360 |
Grade A, and why
create-epics 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 3d 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolution order if omitted:
- Most recent open issue labeled
PRD
Optional environment variables:
GHPM_PROJECT- GitHub Project name to associate Epics with (e.g., "OrgName/ProjectName" or "ProjectName")
<usage_examples> With PRD number:
/ghpm:create-epics prd=#42
Auto-resolve most recent PRD:
/ghpm:create-epics
With project association:
export GHPM_PROJECT="MyOrg/Q1 Roadmap"
/ghpm:create-epics prd=#42
</usage_examples>
<operating_rules>
- Do not ask clarifying questions. If the PRD has ambiguity, encode it as assumptions within each Epic and/or add open questions.
- Do not create local markdown files. All output goes into GitHub issues/comments.
- Each Epic issue must be self-contained for its scope and must reference the PRD by number/link.
- Epics should collectively cover the entire PRD scope without gaps or overlaps.
Epic Count Guidelines
Default to 1 Epic. Only create multiple Epics when the PRD contains truly independent work streams that could be implemented by different people without coordination.
| PRD Type | Epic Count | Justification Required |
|---|---|---|
| Minimal (docs, config, single-file) | 1 | N/A |
| Small (single feature) | 1 | N/A |
| Medium (2-3 independent features) | 2-3 | Each Epic must deliver independent value |
| Large (platform/system) | 3-5 | Each Epic must be separable work stream |
Decision questions before creating multiple Epics:
- Would each Epic deliver independent, usable value if the others were never implemented?
- Could different developers implement each Epic without needing to coordinate on shared code?
- Is there a natural break point where work could pause between Epics?
If the answer to any question is "no", consolidate into fewer Epics.
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.
- 3d ago First seen · 449 lines · 17 tokens per session scan A 556f18f2aff9
create-epics is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 3,600 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-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.