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/primegit 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.01183 |
| Opus 5 | $0.00000 | $0.00592 |
| Sonnet 5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
prime 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prime Context
This command loads essential context for a new agent session by reading the project context documentation and understanding the codebase structure.
Preflight Checklist
Before proceeding, complete these validation steps. Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.
1. Context Availability Check
- Run:
ls -la .claude/context/ 2>/dev/null - If directory doesn't exist or is empty:
- Tell user: "❌ No context found. Please run /context:create first to establish project context."
- Exit gracefully
- Count available context files:
ls -1 .claude/context/*.md 2>/dev/null | wc -l - Report: "📁 Found {count} context files to load"
2. File Integrity Check
- For each context file found:
- Verify file is readable:
test -r ".claude/context/{file}" && echo "readable" - Check file has content:
test -s ".claude/context/{file}" && echo "has content" - Check for valid frontmatter (should start with
---)
- Verify file is readable:
- Report any issues:
- Empty files: "⚠️ {filename} is empty (skipping)"
- Unreadable files: "⚠️ Cannot read {filename} (permission issue)"
- Missing frontmatter: "⚠️ {filename} missing frontmatter (may be corrupted)"
3. Project State Check
- Run:
git status --short 2>/dev/nullto see current state - Run:
git branch --show-current 2>/dev/nullto get current branch - Note if not in git repository (context may be less complete)
Instructions
1. Context Loading Sequence
Load context files in priority order for optimal understanding:
Priority 1 - Essential Context (load first):
project-overview.md- High-level understanding of the projectproject-brief.md- Core purpose and goalstech-context.md- Technical stack and dependencies
Priority 2 - Current State (load second):
4. progress.md - Current status and recent work
5. project-structure.md - Directory and file organization
Priority 3 - Deep Context (load third):
6. system-patterns.md - Architecture and design patterns
7. product-context.md - User needs and requirements
8. project-style-guide.md - Coding conventions
9. project-vision.md - Long-term direction
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 · 147 lines · 0 tokens per session scan A 6220fcb90dc0
prime 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 1,183 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.