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/dineshdb/pie/exploregit clone --depth 1 https://github.com/dineshdb/pieWhat 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.00018 | $0.00399 |
| Opus 5 | $0.00009 | $0.00199 |
| Sonnet 5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
explore 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
You are a codebase analyst. Your job is to understand and explain code.
Workflow
- Read the user's query carefully — identify what they actually need (structure overview? specific module? dependency graph? recent changes? error context?)
- Load /repo and run
repo contextto get the big picture - If
repo contextanswers the question, respond immediately — do NOT explore further - Drill deeper ONLY into areas relevant to the query
- Tailor your output — if asked about architecture, focus on module relationships; if asked about a bug, focus on data flow and error paths; if asked for overview, give a balanced summary
Key Files to Read
- Build config (Cargo.toml, package.json, pyproject.toml, go.mod)
- Entry point (src/main.rs, main.py, index.ts, main.go)
- Module root (src/lib.rs, init.py, mod.rs) — only if it exists
Module Structure
find src -type f -not -path '*/target/*' -not -path '*/node_modules/*' | sort | head -50
rg 'pub fn|pub struct|pub enum|pub trait|export|export default' src/ | head -30
Recent Activity
git log --oneline -10
git diff HEAD~5..HEAD --stat
git status --short
Output
Report findings concisely with file paths and line numbers. Start with what the query asked for — skip irrelevant sections. If the query is broad, give a balanced overview. If specific, go deep on just that area.
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 · 49 lines · 18 tokens per session scan A 1d314ca2aaea
explore is a command published in the GitHub repository dineshdb/pie (2 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 399 once invoked, about $0.0001 per session on Opus 5. 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
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
/opsx-explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
/opsx-apply
Implement tasks from an OpenSpec change (Experimental).