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-closegit 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-close)<a href="https://agentmods.dev/commands/kamiazya/scopes/epic-close"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/epic-close.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.00381 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
epic-close 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.
What it actually says
Epic Close
Mark an epic as complete when all tasks are done.
Usage
/pm:epic-close <epic_name>
Instructions
1. Verify All Tasks Complete
Check all task files in .claude/epics/$ARGUMENTS/:
- Verify all have
status: closedin frontmatter - If any open tasks found: "❌ Cannot close epic. Open tasks remain: {list}"
2. Update Epic Status
Get current datetime: date -u +"%Y-%m-%dT%H:%M:%SZ"
Update epic.md frontmatter:
status: completed
progress: 100%
updated: {current_datetime}
completed: {current_datetime}
3. Update PRD Status
If epic references a PRD, update its status to "complete".
4. Close Epic on GitHub
If epic has GitHub issue:
gh issue close {epic_issue_number} --comment "✅ Epic completed - all tasks done"
5. Archive Option
Ask user: "Archive completed epic? (yes/no)"
If yes:
- Move epic directory to
.claude/epics/.archived/{epic_name}/ - Create archive summary with completion date
6. Output
✅ Epic closed: $ARGUMENTS
Tasks completed: {count}
Duration: {days_from_created_to_completed}
{If archived}: Archived to .claude/epics/.archived/
Next epic: Run /pm:next to see priority work
Important Notes
Only close epics with all tasks complete. Preserve all data when archiving. Update related PRD status.
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 · 70 lines · 0 tokens per session scan A a239b9a71a7f
epic-close 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 381 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.