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-showgit 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/issue-show)<a href="https://agentmods.dev/commands/kamiazya/scopes/issue-show"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/issue-show.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.00621 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
issue-show 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Show
Display issue and sub-issues with detailed information.
Usage
/pm:issue-show <issue_number>
Instructions
You are displaying comprehensive information about a GitHub issue and related sub-issues for: Issue #$ARGUMENTS
1. Fetch Issue Data
- Use
gh issue view #$ARGUMENTSto get GitHub issue details - Look for local task file: first check
.claude/epics/*/$ARGUMENTS.md(new naming) - If not found, search for file with
github:.*issues/$ARGUMENTSin frontmatter (old naming) - Check for related issues and sub-tasks
2. Issue Overview
Display issue header:
🎫 Issue #$ARGUMENTS: {Issue Title}
Status: {open/closed}
Labels: {labels}
Assignee: {assignee}
Created: {creation_date}
Updated: {last_update}
📝 Description:
{issue_description}
3. Local File Mapping
If local task file exists:
📁 Local Files:
Task file: .claude/epics/{epic_name}/{task_file}
Updates: .claude/epics/{epic_name}/updates/$ARGUMENTS/
Last local update: {timestamp}
4. Sub-Issues and Dependencies
Show related issues:
🔗 Related Issues:
Parent Epic: #{epic_issue_number}
Dependencies: #{dep1}, #{dep2}
Blocking: #{blocked1}, #{blocked2}
Sub-tasks: #{sub1}, #{sub2}
5. Recent Activity
Display recent comments and updates:
💬 Recent Activity:
{timestamp} - {author}: {comment_preview}
{timestamp} - {author}: {comment_preview}
View full thread: gh issue view #$ARGUMENTS --comments
6. Progress Tracking
If task file exists, show progress:
✅ Acceptance Criteria:
✅ Criterion 1 (completed)
🔄 Criterion 2 (in progress)
⏸️ Criterion 3 (blocked)
□ Criterion 4 (not started)
7. Quick Actions
🚀 Quick Actions:
Start work: /pm:issue-start $ARGUMENTS
Sync updates: /pm:issue-sync $ARGUMENTS
Add comment: gh issue comment #$ARGUMENTS --body "your comment"
View in browser: gh issue view #$ARGUMENTS --web
8. Error Handling
- Handle invalid issue numbers gracefully
- Check for network/authentication issues
- Provide helpful error messages and alternatives
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 · 92 lines · 0 tokens per session scan A d33a1b6d053a
issue-show 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 621 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.