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-editgit clone --depth 1 https://github.com/kamiazya/scopesWhat 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.00331 |
| Opus 5 | $0.00000 | $0.00166 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
epic-edit 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 2d 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.
What it actually says
Epic Edit
Edit epic details after creation.
Usage
/pm:epic-edit <epic_name>
Instructions
1. Read Current Epic
Read .claude/epics/$ARGUMENTS/epic.md:
- Parse frontmatter
- Read content sections
2. Interactive Edit
Ask user what to edit:
- Name/Title
- Description/Overview
- Architecture decisions
- Technical approach
- Dependencies
- Success criteria
3. Update Epic File
Get current datetime: date -u +"%Y-%m-%dT%H:%M:%SZ"
Update epic.md:
- Preserve all frontmatter except
updated - Apply user's edits to content
- Update
updatedfield with current datetime
4. Option to Update GitHub
If epic has GitHub URL in frontmatter: Ask: "Update GitHub issue? (yes/no)"
If yes:
gh issue edit {issue_number} --body-file .claude/epics/$ARGUMENTS/epic.md
5. Output
✅ Updated epic: $ARGUMENTS
Changes made to: {sections_edited}
{If GitHub updated}: GitHub issue updated ✅
View epic: /pm:epic-show $ARGUMENTS
Important Notes
Preserve frontmatter history (created, github URL, etc.).
Don't change task files when editing epic.
Follow /rules/frontmatter-operations.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.
- 2d ago First seen · 67 lines · 0 tokens per session scan A 5f3660d642f4
epic-edit 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 331 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.