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/kamiazya/scopes/epic-startgit clone --depth 1 https://github.com/kamiazya/scopesWrote 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/kamiazya/scopes/epic-start)<a href="https://agentmods.dev/commands/kamiazya/scopes/epic-start"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/epic-start.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 | $0.00000 | $0.01560 |
| Opus 5 | $0.00000 | $0.00780 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
epic-start 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Start
Launch parallel agents to work on epic tasks in a shared branch.
Usage
/pm:epic-start <epic_name>
Quick Check
-
Verify epic exists:
test -f .claude/epics/$ARGUMENTS/epic.md || echo "❌ Epic not found. Run: /pm:prd-parse $ARGUMENTS" -
Check GitHub sync: Look for
github:field in epic frontmatter. If missing: "❌ Epic not synced. Run: /pm:epic-sync $ARGUMENTS first" -
Check for branch:
git branch -a | grep "epic/$ARGUMENTS" -
Check for uncommitted changes:
git status --porcelainIf output is not empty: "❌ You have uncommitted changes. Please commit or stash them before starting an epic"
Instructions
1. Create or Enter Branch
Follow /rules/branch-operations.md:
# Check for uncommitted changes
if [ -n "$(git status --porcelain)" ]; then
echo "❌ You have uncommitted changes. Please commit or stash them before starting an epic."
exit 1
fi
# If branch doesn't exist, create it
if ! git branch -a | grep -q "epic/$ARGUMENTS"; then
git checkout main
git pull origin main
git checkout -b epic/$ARGUMENTS
git push -u origin epic/$ARGUMENTS
echo "✅ Created branch: epic/$ARGUMENTS"
else
git checkout epic/$ARGUMENTS
git pull origin epic/$ARGUMENTS
echo "✅ Using existing branch: epic/$ARGUMENTS"
fi
2. Identify Ready Issues
Read all task files in .claude/epics/$ARGUMENTS/:
- Parse frontmatter for
status,depends_on,parallelfields - Check GitHub issue status if needed
- Build dependency graph
Categorize issues:
- Ready: No unmet dependencies, not started
- Blocked: Has unmet dependencies
- In Progress: Already being worked on
- Complete: Finished
3. Analyze Ready Issues
For each ready issue without analysis:
# Check for analysis
if ! test -f .claude/epics/$ARGUMENTS/{issue}-analysis.md; then
echo "Analyzing issue #{issue}..."
# Run analysis (inline or via Task tool)
fi
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 · 248 lines · 0 tokens per session scan A 78052a15d506
epic-start is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,560 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-31.
Other commands, from other repositories
diagnose-deeptrace
Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.
troubleshoot-experience
Troubleshoot a user's digital experience using ZDX scores, metrics, and network path data.
app-health
Analyze application health across the organization using ZDX scores and metrics.
audit-software
Audit software inventory across devices using ZDX data for compliance and vulnerability assessment.
compare-locations
Compare digital experience across locations, departments, or geolocations using ZDX.
investigate-alerts
Investigate active and historical ZDX alerts to understand scope, root cause, and impact.