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-refreshgit 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.00695 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
epic-refresh 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Refresh
Update epic progress based on task states.
Usage
/pm:epic-refresh <epic_name>
Instructions
1. Count Task Status
Scan all task files in .claude/epics/$ARGUMENTS/:
- Count total tasks
- Count tasks with
status: closed - Count tasks with
status: open - Count tasks with work in progress
2. Calculate Progress
progress = (closed_tasks / total_tasks) * 100
Round to nearest integer.
3. Update GitHub Task List
If epic has GitHub issue, sync task checkboxes:
# Get epic issue number from epic.md frontmatter
epic_issue={extract_from_github_field}
if [ ! -z "$epic_issue" ]; then
# Get current epic body
gh issue view $epic_issue --json body -q .body > /tmp/epic-body.md
# For each task, check its status and update checkbox
for task_file in .claude/epics/$ARGUMENTS/[0-9]*.md; do
task_issue=$(grep 'github:' $task_file | grep -oE '[0-9]+$')
task_status=$(grep 'status:' $task_file | cut -d: -f2 | tr -d ' ')
if [ "$task_status" = "closed" ]; then
# Mark as checked
sed -i "s/- \[ \] #$task_issue/- [x] #$task_issue/" /tmp/epic-body.md
else
# Ensure unchecked (in case manually checked)
sed -i "s/- \[x\] #$task_issue/- [ ] #$task_issue/" /tmp/epic-body.md
fi
done
# Update epic issue
gh issue edit $epic_issue --body-file /tmp/epic-body.md
fi
4. Determine Epic Status
- If progress = 0% and no work started:
backlog - If progress > 0% and < 100%:
in-progress - If progress = 100%:
completed
5. Update Epic
Get current datetime: date -u +"%Y-%m-%dT%H:%M:%SZ"
Update epic.md frontmatter:
status: {calculated_status}
progress: {calculated_progress}%
updated: {current_datetime}
6. Output
🔄 Epic refreshed: $ARGUMENTS
Tasks:
Closed: {closed_count}
Open: {open_count}
Total: {total_count}
Progress: {old_progress}% → {new_progress}%
Status: {old_status} → {new_status}
GitHub: Task list updated ✓
{If complete}: Run /pm:epic-close $ARGUMENTS to close epic
{If in progress}: Run /pm:next to see priority tasks
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 · 103 lines · 0 tokens per session scan A 9fd477caf71c
epic-refresh 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 695 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.