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/syncgit 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.00504 |
| Opus 5 | $0.00000 | $0.00252 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
sync 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 yesterday.
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
Sync
Full bidirectional sync between local and GitHub.
Usage
/pm:sync [epic_name]
If epic_name provided, sync only that epic. Otherwise sync all.
Instructions
1. Pull from GitHub
Get current state of all issues:
# Get all epic and task issues
gh issue list --label "epic" --limit 1000 --json number,title,state,body,labels,updatedAt
gh issue list --label "task" --limit 1000 --json number,title,state,body,labels,updatedAt
2. Update Local from GitHub
For each GitHub issue:
- Find corresponding local file by issue number
- Compare states:
- If GitHub state newer (updatedAt > local updated), update local
- If GitHub closed but local open, close local
- If GitHub reopened but local closed, reopen local
- Update frontmatter to match GitHub state
3. Push Local to GitHub
For each local task/epic:
- If has GitHub URL but GitHub issue not found, it was deleted - mark local as archived
- If no GitHub URL, create new issue (like epic-sync)
- If local updated > GitHub updatedAt, push changes:
gh issue edit {number} --body-file {local_file}
4. Handle Conflicts
If both changed (local and GitHub updated since last sync):
- Show both versions
- Ask user: "Local and GitHub both changed. Keep: (local/github/merge)?"
- Apply user's choice
5. Update Sync Timestamps
Update all synced files with last_sync timestamp.
6. Output
🔄 Sync Complete
Pulled from GitHub:
Updated: {count} files
Closed: {count} issues
Pushed to GitHub:
Updated: {count} issues
Created: {count} new issues
Conflicts resolved: {count}
Status:
✅ All files synced
{or list any sync failures}
Important Notes
Follow /rules/github-operations.md for GitHub commands.
Follow /rules/frontmatter-operations.md for local updates.
Always backup before sync in case of issues.
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.
- yesterday First seen · 83 lines · 0 tokens per session scan A 2799ad79df2d
sync 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 504 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.
create-access-rule
Create a ZPA access policy rule with v2 conditions for application access control.
investigate-incident
Investigate security incidents using Z-Insights analytics -- threats, firewall actions, shadow IT, and web traffic.