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/issue-statusgit 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.00499 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
issue-status 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
Issue Status
Check issue status (open/closed) and current state.
Usage
/pm:issue-status <issue_number>
Instructions
You are checking the current status of a GitHub issue and providing a quick status report for: Issue #$ARGUMENTS
1. Fetch Issue Status
Use GitHub CLI to get current status:
gh issue view #$ARGUMENTS --json state,title,labels,assignees,updatedAt
2. Status Display
Show concise status information:
🎫 Issue #$ARGUMENTS: {Title}
📊 Status: {OPEN/CLOSED}
Last update: {timestamp}
Assignee: {assignee or "Unassigned"}
🏷️ Labels: {label1}, {label2}, {label3}
3. Epic Context
If issue is part of an epic:
📚 Epic Context:
Epic: {epic_name}
Epic progress: {completed_tasks}/{total_tasks} tasks complete
This task: {task_position} of {total_tasks}
4. Local Sync Status
Check if local files are in sync:
💾 Local Sync:
Local file: {exists/missing}
Last local update: {timestamp}
Sync status: {in_sync/needs_sync/local_ahead/remote_ahead}
5. Quick Status Indicators
Use clear visual indicators:
- 🟢 Open and ready
- 🟡 Open with blockers
- 🔴 Open and overdue
- ✅ Closed and complete
- ❌ Closed without completion
6. Actionable Next Steps
Based on status, suggest actions:
🚀 Suggested Actions:
- Start work: /pm:issue-start $ARGUMENTS
- Sync updates: /pm:issue-sync $ARGUMENTS
- Close issue: gh issue close #$ARGUMENTS
- Reopen issue: gh issue reopen #$ARGUMENTS
7. Batch Status
If checking multiple issues, support comma-separated list:
/pm:issue-status 123,124,125
Keep the output concise but informative, perfect for quick status checks during development of Issue #$ARGUMENTS.
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 · 79 lines · 0 tokens per session scan A 542ad54e5634
issue-status 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 499 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.