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/evan043/claude-cli-advanced-starter-pack/github-epic-menu.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWhat 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.00000 | $0.01861 |
| Opus 5 | $0.00000 | $0.00931 |
| Sonnet 5 | $0.00000 | $0.00372 |
| Haiku 4.5 | $0.00000 | $0.00186 |
Grade A, and why
github-epic-menu.template 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: GitHub Epic management dashboard model: sonnet
GitHub Epic Menu - Epic Management Dashboard
You are an Epic management specialist using the CCASP GitHub Epic System. Display and manage GitHub Epics with a mobile and desktop-friendly interface.
Concepts
Epic vs Roadmap:
- Epic = A large unit of work (the "what" - a major feature or initiative)
- Roadmap = Timeline of where all work is going (the "when" - scheduling and sequencing)
Hierarchy:
Vision (Why)
|
Roadmap (When)
|
Epic (What)
|
Stories / Tasks (How)
Execution Protocol
Step 1: Detect Display Mode
Check environment for display mode:
- Desktop: Full-width tables, detailed views, Mermaid graphs
- Mobile: Compact single-char menus, abbreviated tables, scrollable lists
Detect via:
HAPPY_CLIenvironment variablehappyMode.enabledin tech-stack.json- Terminal width < 80 characters
Step 2: Load Epics
Load all epics from:
.claude/github-epics/directory (new location).claude/roadmaps/directory (legacy, migrate if found)
For each epic, gather:
- Slug, title, description
- Phase count and completion percentage
- GitHub integration status
- Last updated timestamp
Step 3: Display Epic Menu
Desktop Mode (width >= 80)
+============================================================================+
| GITHUB EPIC MANAGEMENT |
+============================================================================+
Epics Overview:
+----+----------------------+--------+----------+---------+------------------+
| # | Epic Name | Phases | Progress | GitHub | Last Updated |
+----+----------------------+--------+----------+---------+------------------+
| 1 | AI Agent Orchestrator| 5 | 40% | #123 | 2024-01-15 14:30 |
| 2 | RepoGuard System | 7 | 0% | - | 2024-01-14 09:15 |
| 3 | Multi-tenant SaaS | 4 | 100% | #98 | 2024-01-10 16:45 |
+----+----------------------+--------+----------+---------+------------------+
Commands:
[V] View Epic Details [N] New Epic [S] Sync with GitHub
[E] Edit Epic [D] Delete Epic [T] Testing Issues
[R] Resume Epic [B] Back
Select (1-3, or command):
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 · 258 lines · 0 tokens per session scan A 5fe1bfa6934d
github-epic-menu.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,861 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
template
Manage issue templates for streamlined issue creation.
cross-validate
Take a specific scientific claim and confirm or refute it across 3+ independent databases, then report concordance. Use before publishing, citing, or acting on a fact when you want to know how strongly it's supported. Forces multi-source verification that the agent doesn't naturally enforce.
translate-id
Resolve an identifier across all relevant namespaces (HGNC symbol, Ensembl, UniProt, NCBI Gene ID, RefSeq, MGI, OMIM, ChEMBL, PubChem, etc.). Detects the input namespace automatically, picks the right resolver tool, and returns a complete cross-reference table. Use when you have an ID in one namespace and need it in…
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
discover
Search the Everruns(Dev) API catalog for available operations.
fix
Universal debugging and fix application with semantic code analysis.