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-start-worktreegit 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-worktree)<a href="https://agentmods.dev/commands/kamiazya/scopes/epic-start-worktree"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/epic-start-worktree.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.01408 |
| Opus 5 | $0.00000 | $0.00704 |
| Sonnet 5 | $0.00000 | $0.00282 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
epic-start-worktree 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 — 222 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 worktree.
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 worktree:
git worktree list | grep "epic-$ARGUMENTS"
Instructions
1. Create or Enter Worktree
Follow /rules/worktree-operations.md:
# If worktree doesn't exist, create it
if ! git worktree list | grep -q "epic-$ARGUMENTS"; then
git checkout main
git pull origin main
git worktree add ../epic-$ARGUMENTS -b epic/$ARGUMENTS
echo "✅ Created worktree: ../epic-$ARGUMENTS"
else
echo "✅ Using existing worktree: ../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
4. Launch Parallel Agents
For each ready issue with analysis:
## Starting Issue #{issue}: {title}
Reading analysis...
Found {count} parallel streams:
- Stream A: {description} (Agent-{id})
- Stream B: {description} (Agent-{id})
Launching agents in worktree: ../epic-$ARGUMENTS/
Use Task tool to launch each stream:
Task:
description: "Issue #{issue} Stream {X}"
subagent_type: "{agent_type}"
prompt: |
Working in worktree: ../epic-$ARGUMENTS/
Issue: #{issue} - {title}
Stream: {stream_name}
Your scope:
- Files: {file_patterns}
- Work: {stream_description}
Read full requirements from:
- .claude/epics/$ARGUMENTS/{task_file}
- .claude/epics/$ARGUMENTS/{issue}-analysis.md
Follow coordination rules in /rules/agent-coordination.md
Commit frequently with message format:
"Issue #{issue}: {specific change}"
Update progress in:
.claude/epics/$ARGUMENTS/updates/{issue}/stream-{X}.md
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 · 222 lines · 0 tokens per session scan A ac216809e567
epic-start-worktree 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,408 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.
investigate-sandbox
Investigate ZIA Sandbox file analysis -- check sandbox reports, quota, SSL prerequisite, and diagnose file block/quarantine issues.
troubleshoot-user
Cross-product troubleshooting of user connectivity across ZCC, ZDX, ZPA, and ZIA.
investigate-incident
Investigate security incidents using Z-Insights analytics -- threats, firewall actions, shadow IT, and web traffic.
create-access-rule
Create a ZPA access policy rule with v2 conditions for application access control.