github-epic-status.template

github-epic-status.template is a command for coding agents from evan043/claude-cli-advanced-starter-pack. It costs 0 tokens per session (3,534 once invoked), scanned A, original, MIT.

A command prompt for showing progress across a GitHub epic and its nested work items. A GitHub epic is a large body of work that can contain roadmaps, phases, and tasks.

In plain words
What is it for?
It is for displaying epic progress, including child roadmaps, development plans, phases, and tasks, with progress indicators and follow-up insights.
Why use it?
It gathers progress from the hierarchy so the status of a large initiative can be viewed in one place.

Command

Install

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.

agentmods
npx agentmods add commands/evan043/claude-cli-advanced-starter-pack/github-epic-status.template
Clone the repo
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-pack

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.

agentmods badge for github-epic-status.template

README.md
[![agentmods](https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/github-epic-status.template.svg)](https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/github-epic-status.template)
Your own site
<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/github-epic-status.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/github-epic-status.template.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,534 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03534
Opus 5 $0.00000 $0.01767
Sonnet 5 $0.00000 $0.00707
Haiku 4.5 $0.00000 $0.00353

Measured 4d ago against content hash a33b3bab354a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-epic-status.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 4d 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.

templates/commands/github-epic-status.template.md · 389 lines

How it starts

The opening of the file, as written. The whole thing — 389 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 progress dashboard model: haiku

GitHub Epic Status - Hierarchy Progress Dashboard

You are an Epic progress tracking specialist. Display comprehensive status for the entire epic hierarchy showing epic → roadmaps → phase-dev-plans → phases → tasks with visual progress indicators and actionable insights.

Execution Protocol

Step 1: Load Epic Data and Hierarchy

Load epic and aggregate all child progress:

import { loadEpic, loadOrchestratorState } from './src/epic/state-manager.js';
import { aggregateEpicProgress } from './src/orchestration/progress-aggregator.js';

const epic = loadEpic(projectRoot, epicSlug);
const state = loadOrchestratorState(projectRoot, epicSlug);

if (!epic) {
  console.error('Epic not found');
  return;
}

// Aggregate progress from all roadmaps
const epicPath = `.claude/epics/${epicSlug}`;
const progress = aggregateEpicProgress(epicPath);

Step 2: Display Overview (All Epics)

When no slug provided (/github-epic-status), show summary table:

╔═══════════════════════════════════════════════════════════════════════════════╗
║                          GITHUB EPIC STATUS DASHBOARD                          ║
╠═══════════════════════════════════════════════════════════════════════════════╣
║                                                                                 ║
║  Active Epics: 2            Completed: 1            Total Roadmaps: 12          ║
║                                                                                 ║
╠───────────────────────────────────────────────────────────────────────────────╣
║ # │ Epic Name                │ Roadmaps │ Progress    │ Status      │ Next     ║
╠───────────────────────────────────────────────────────────────────────────────╣
║ 1 │ Multi-Tenant Auth System │ 3/3      │ ██████████ 100% │ completed   │ -    ║
║ 2 │ Dashboard Refactor       │ 2/4      │ ████░░░░░░ 50%  │ active      │ RM 3 ║
║ 3 │ API v2 Migration         │ 0/5      │ ░░░░░░░░░░ 0%   │ not_started │ RM 1 ║
╚═══════════════════════════════════════════════════════════════════════════════╝

Commands:
  /github-epic-status {slug}  - View detailed epic status
  /epic-advance {slug}        - Advance to next roadmap

Read the full file on GitHub · 389 lines

Changes

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.

  1. 4d ago First seen · 389 lines · 0 tokens per session scan A a33b3bab354a

Subscribe to this mod's changes

github-epic-status.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 3,534 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.