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-editgit 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.00366 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
issue-edit 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
Issue Edit
Edit issue details locally and on GitHub.
Usage
/pm:issue-edit <issue_number>
Instructions
1. Get Current Issue State
# Get from GitHub
gh issue view $ARGUMENTS --json title,body,labels
# Find local task file
# Search for file with github:.*issues/$ARGUMENTS
2. Interactive Edit
Ask user what to edit:
- Title
- Description/Body
- Labels
- Acceptance criteria (local only)
- Priority/Size (local only)
3. Update Local File
Get current datetime: date -u +"%Y-%m-%dT%H:%M:%SZ"
Update task file with changes:
- Update frontmatter
nameif title changed - Update body content if description changed
- Update
updatedfield with current datetime
4. Update GitHub
If title changed:
gh issue edit $ARGUMENTS --title "{new_title}"
If body changed:
gh issue edit $ARGUMENTS --body-file {updated_task_file}
If labels changed:
gh issue edit $ARGUMENTS --add-label "{new_labels}"
gh issue edit $ARGUMENTS --remove-label "{removed_labels}"
5. Output
✅ Updated issue #$ARGUMENTS
Changes:
{list_of_changes_made}
Synced to GitHub: ✅
Important Notes
Always update local first, then GitHub.
Preserve frontmatter fields not being edited.
Follow /rules/frontmatter-operations.md.
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 · 77 lines · 0 tokens per session scan A 9f7fa919463f
issue-edit 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 366 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.