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/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/epic-advance.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/epic-advance.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/epic-advance.template.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.03179 |
| Opus 5 | $0.00000 | $0.01589 |
| Sonnet 5 | $0.00000 | $0.00636 |
| Haiku 4.5 | $0.00000 | $0.00318 |
Grade A, and why
epic-advance.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 8d 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 — 429 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: Advance epic to next roadmap model: sonnet
Epic Advance - Manual Epic Progression
You are an Epic execution specialist. Allow manual advancement through epic roadmaps with gating override support and decision logging.
Purpose
This command provides manual control over epic progression when:
- Automatic gating is blocking advancement
- User wants to skip ahead to a specific roadmap
- Testing results need manual review
- Override is needed for development/debugging
Execution Protocol
Step 1: Load Epic State
Load epic and orchestrator state:
import { loadEpic, loadOrchestratorState } from './src/epic/state-manager.js';
import { getNextRoadmap } from './src/epic/schema.js';
const epic = loadEpic(projectRoot, epicSlug);
const state = loadOrchestratorState(projectRoot, epicSlug);
if (!epic) {
console.error('Epic not found');
return;
}
Step 2: Display Current Position
Show user where they are in the epic:
╔═══════════════════════════════════════════════════════════════════════╗
║ EPIC POSITION: {epic_name} ║
╠═══════════════════════════════════════════════════════════════════════╣
║ ║
║ Overall Progress: {completion_percentage}% ║
║ Current Roadmap Index: {current_roadmap_index + 1}/{total_roadmaps} ║
║ ║
╠───────────────────────────────────────────────────────────────────────╣
║ ROADMAP STATUS ║
╠───────────────────────────────────────────────────────────────────────╣
║ ║
║ ✓ Roadmap 1: {title} (100% - COMPLETED) ║
║ ✓ Roadmap 2: {title} (100% - COMPLETED) ║
║ → Roadmap 3: {title} (45% - IN PROGRESS) ← CURRENT ║
║ ⬜ Roadmap 4: {title} (0% - PENDING) ║
║ ⬜ Roadmap 5: {title} (0% - PENDING) ║
║ ║
╚═══════════════════════════════════════════════════════════════════════╝
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.
- 8d ago First seen · 429 lines · 0 tokens per session scan A 921b38426297
epic-advance.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,179 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
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
update-docs
Scan for recently modified files and update corresponding documentation.
handoff
Create a handoff document for seamless session continuity.
board-csk
Team board — see who holds which item, claim one, hand it over, complete it.
queue
Queue a question or coding task for claude-overnight to run when your limits reset.