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-reopengit 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-reopen)<a href="https://agentmods.dev/commands/kamiazya/scopes/issue-reopen"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/issue-reopen.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.00345 |
| Opus 5 | $0.00000 | $0.00172 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
issue-reopen 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 4d 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 Reopen
Reopen a closed issue.
Usage
/pm:issue-reopen <issue_number> [reason]
Instructions
1. Find Local Task File
Search for task file with github:.*issues/$ARGUMENTS in frontmatter.
If not found: "❌ No local task for issue #$ARGUMENTS"
2. Update Local Status
Get current datetime: date -u +"%Y-%m-%dT%H:%M:%SZ"
Update task file frontmatter:
status: open
updated: {current_datetime}
3. Reset Progress
If progress file exists:
- Keep original started date
- Reset completion to previous value or 0%
- Add note about reopening with reason
4. Reopen on GitHub
# Reopen with comment
echo "🔄 Reopening issue
Reason: $ARGUMENTS
---
Reopened at: {timestamp}" | gh issue comment $ARGUMENTS --body-file -
# Reopen the issue
gh issue reopen $ARGUMENTS
5. Update Epic Progress
Recalculate epic progress with this task now open again.
6. Output
🔄 Reopened issue #$ARGUMENTS
Reason: {reason_if_provided}
Epic progress: {updated_progress}%
Start work with: /pm:issue-start $ARGUMENTS
Important Notes
Preserve work history in progress files. Don't delete previous progress, just reset 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.
- 4d ago First seen · 71 lines · 0 tokens per session scan A 7853839f57b4
issue-reopen 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 345 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.
troubleshoot-user
Cross-product troubleshooting of user connectivity across ZCC, ZDX, ZPA, and ZIA.
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.
onboard-app
End-to-end onboarding of a new application in ZPA with full dependency chain.