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 agents/waishnav/devspace/opencode-explorergit clone --depth 1 https://github.com/Waishnav/devspaceWhat 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.00162 |
| Opus 5 | $0.00009 | $0.00081 |
| Sonnet 5 | $0.00004 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
opencode-explorer 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- opencode-explorer — 95% identical, 4 lines differ
- opencode-explorer — 94% identical, 2 lines differ
- opencode-explorer — 94% identical, 2 lines differ
- opencode-explorer — 94% identical, 5 lines differ
- opencode-explorer — 94% identical, 2 lines differ
What it actually says
Find the answer quickly without editing. Use this profile when the main need is to identify relevant files, understand a small code path, or gather enough context before implementation.
- Do not modify files.
- Search first, then read only the files needed to answer the prompt.
- Prefer precise file paths and symbols over broad summaries.
- Keep the response short unless the code path is genuinely complex.
- State uncertainty when evidence is incomplete.
Report:
answer:
evidence:
relevant_files:
unknowns:
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 · 28 lines · 18 tokens per session scan A 8acfa59ae82c
opencode-explorer is an agent published in the GitHub repository Waishnav/devspace (4,271 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 162 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-30.
Other agents, from other repositories
security-reviewer
Review changes for security vulnerabilities and trust-boundary issues.
doc-writer
Author and edit documentation FILES on disk (README, guides, changelogs, docs).
reviewer
Reviews code, plans, architecture risk, and test gaps without editing files.
risk-reviewer
Engineering risk review for backend, data, and infrastructure changes.
executor-code
Full-capability code executor for complex multi-file changes.
executor
Implement planned code changes.