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/phase-track.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/phase-track.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/phase-track.template/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/phase-track.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/phase-track.template.svg" alt="Reviewed on agentmods" width="80" 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.06627 |
| Opus 5.5 | $0.00000 | $0.02651 |
| Sonnet 5.5 | $0.00000 | $0.01325 |
| Haiku 4.5 | $0.00000 | $0.00663 |
Grade B, and why
phase-track.template scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find .claude/roadmaps -name "phase-*.json" -type f 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 742 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: Track progress of phased development plans model: haiku
/phase-track - Phased Development Progress Tracker
View and update progress on phased development plans.
HARD SEQUENTIAL GATES (NON-NEGOTIABLE)
Phases execute ONE AT A TIME. Phase N+1 CANNOT start until Phase N status = completed in PROGRESS.json.
FORBIDDEN - Will Cause Context Overflow and Lost Work:
- DO NOT start Phase N+1 while Phase N is still
in_progress - DO NOT launch multiple phases in parallel (even via background agents)
- DO NOT launch tasks from different phases simultaneously
- DO NOT skip a phase that failed validation and continue to the next
- DO NOT interpret "run-all" as "run all at once" — it means "run all sequentially, one at a time"
REQUIRED - Hard Gate Protocol:
- ONE phase at a time: Execute all tasks in Phase N → verify all complete → mark Phase N
completed→ THEN start Phase N+1 - Verify via PROGRESS.json: Read the file to confirm
status: "completed"before advancing — do not rely on memory - Context checkpoint: Before EACH phase, check context usage. If >70%, STOP and offer /compact
- Failure = Full Stop: If a task or phase fails, HALT execution. Do NOT continue to the next phase. Report the error and wait for user input
- File is source of truth: Write to PROGRESS.json after EVERY task completion. If the session crashes, progress is preserved
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.
- 1mo ago First seen · 742 lines · 0 tokens per session scan B ff1b26211637
phase-track.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,627 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
story-6.1.4
Story ID: 6.1.4 Epic: Epic-6.1 - Agent Identity System Wave: Wave 1 (Foundation) Status: 📋 Ready to Start Priority: 🔴 Critical Owner: Dev (Dex) Created: 2025-01-14 Updated: 2025-01-17 (v4 - Unified System Integration) Duration: 2.5 days (20 hours) Investment: $250.00.
handoff
Write a session handoff document for continuity.
update-docs
Scan recently modified files and update the matching documentation.