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/cleangit 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.00496 |
| Opus 5 | $0.00000 | $0.00248 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
clean 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
Clean
Clean up completed work and archive old epics.
Usage
/pm:clean [--dry-run]
Options:
--dry-run- Show what would be cleaned without doing it
Instructions
1. Identify Completed Epics
Find epics with:
status: completedin frontmatter- All tasks closed
- Last update > 30 days ago
2. Identify Stale Work
Find:
- Progress files for closed issues
- Update directories for completed work
- Orphaned task files (epic deleted)
- Empty directories
3. Show Cleanup Plan
🧹 Cleanup Plan
Completed Epics to Archive:
{epic_name} - Completed {days} days ago
{epic_name} - Completed {days} days ago
Stale Progress to Remove:
{count} progress files for closed issues
Empty Directories:
{list_of_empty_dirs}
Space to Recover: ~{size}KB
{If --dry-run}: This is a dry run. No changes made.
{Otherwise}: Proceed with cleanup? (yes/no)
4. Execute Cleanup
If user confirms:
Archive Epics:
mkdir -p .claude/epics/.archived
mv .claude/epics/{completed_epic} .claude/epics/.archived/
Remove Stale Files:
- Delete progress files for closed issues > 30 days
- Remove empty update directories
- Clean up orphaned files
Create Archive Log:
Create .claude/epics/.archived/archive-log.md:
# Archive Log
## {current_date}
- Archived: {epic_name} (completed {date})
- Removed: {count} stale progress files
- Cleaned: {count} empty directories
5. Output
✅ Cleanup Complete
Archived:
{count} completed epics
Removed:
{count} stale files
{count} empty directories
Space recovered: {size}KB
System is clean and organized.
Important Notes
Always offer --dry-run to preview changes. Never delete PRDs or incomplete work. Keep archive log for history.
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 fd25c66b5006
clean 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 496 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
review.v1
Review code changes: /review [commit|branch|PR].
diagnose-deeptrace
Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.
troubleshoot-user
Cross-product troubleshooting of user connectivity across ZCC, ZDX, ZPA, and ZIA.
audit-ssl
Audit ZIA SSL inspection rules -- list rules by action (INSPECT, DONOTINSPECT, DONOTDECRYPT, BLOCK), identify bypasses, and assess risk.
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.