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/importgit 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.00570 |
| Opus 5 | $0.00000 | $0.00285 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
import 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
Import
Import existing GitHub issues into the PM system.
Usage
/pm:import [--epic <epic_name>] [--label <label>]
Options:
--epic- Import into specific epic--label- Import only issues with specific label- No args - Import all untracked issues
Instructions
1. Fetch GitHub Issues
# Get issues based on filters
if [[ "$ARGUMENTS" == *"--label"* ]]; then
gh issue list --label "{label}" --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt
else
gh issue list --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt
fi
2. Identify Untracked Issues
For each GitHub issue:
- Search local files for matching github URL
- If not found, it's untracked and needs import
3. Categorize Issues
Based on labels:
- Issues with "epic" label → Create epic structure
- Issues with "task" label → Create task in appropriate epic
- Issues with "epic:{name}" label → Assign to that epic
- No PM labels → Ask user or create in "imported" epic
4. Create Local Structure
For each issue to import:
If Epic:
mkdir -p .claude/epics/{epic_name}
# Create epic.md with GitHub content and frontmatter
If Task:
# Find next available number (001.md, 002.md, etc.)
# Create task file with GitHub content
Set frontmatter:
name: {issue_title}
status: {open|closed based on GitHub}
created: {GitHub createdAt}
updated: {GitHub updatedAt}
github: https://github.com/{org}/{repo}/issues/{number}
imported: true
5. Output
📥 Import Complete
Imported:
Epics: {count}
Tasks: {count}
Created structure:
{epic_1}/
- {count} tasks
{epic_2}/
- {count} tasks
Skipped (already tracked): {count}
Next steps:
Run /pm:status to see imported work
Run /pm:sync to ensure full synchronization
Important Notes
Preserve all GitHub metadata in frontmatter.
Mark imported files with imported: true flag.
Don't overwrite existing local files.
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 · 99 lines · 0 tokens per session scan A cd2c7a3b3eef
import 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 570 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.