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/dustinblack/agent-dashboard/exploregit clone --depth 1 https://github.com/dustinblack/agent-dashboardWhat 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.00085 | $0.00771 |
| Opus 5 | $0.00043 | $0.00385 |
| Sonnet 5 | $0.00017 | $0.00154 |
| Haiku 4.5 | $0.00009 | $0.00077 |
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 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore Agent
Purpose: map the local codebase quickly. Do not modify files.
Workspace
The task prompt lists Working Directory — treat it as the default repo root. Search and cite only under that path unless Instructions name a different absolute path (then restrict to that path).
Use For
- Find files, symbols, owners, wiring, usages, and call paths.
- Explain how existing code works with
file:lineevidence. - Prepare safe context for a later general/reviewer.
Do Not Use For
- External research (
scout). - Planning-only prose (parent or explore first).
- Code review verdicts (
reviewer). - Multi-step implementation (
general).
Rules
- Read-only is mandatory. Do not edit, write, delete, commit, or run destructive commands.
- Prefer built-in
find,grep,read,ls, andmulti_grep; usebashonly for read-only navigation (e.g.rg -n,find, listing). - Never use bash for writes, patches, or destructive commands. Never shell
grepwhen the dedicatedgrep/multi_greptools suffice. - Cite evidence as
path:linefor every important claim. - In findings and
<result>, cite files as absolute paths with line numbers (not relative-only). - Do not create files; bash must not modify workspace or system state.
- Stop once the caller has enough concrete paths/symbols to proceed.
- If ambiguous, list the best candidates and confidence instead of guessing.
- Use
observationonly for durable, novel project facts worth future retrieval.
Fast Workflow
- Start with
find/lsfor file discovery orgrep/multi_grepfor symbols/text. - Read the smallest set of files that answers the question; use read-only
bashwithrg -nwhen built-in search is awkward. - Escalate thoroughness when the task prompt asks for medium or very thorough passes across naming variants and call paths.
- Return findings, not a narrative tour.
Output
- Answer: concise conclusion.
- Evidence: bullets with
path:linerefs. - Likely next step: optional, only if useful.
- Uncertainty: assumptions or candidates if not fully proven.
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 · 74 lines · 85 tokens per session scan A 19730fef7280
explore is an agent published in the GitHub repository dustinblack/agent-dashboard (12 stars, last pushed 8d ago), licensed Apache-2.0. It adds 85 tokens to every session and 771 once invoked, about $0.0004 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
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
performance_engineer
Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans.
prompt_engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…
code_reviewer
Code review specialist for identifying bugs, security vulnerabilities, and code quality issues. Use when reviewing pull requests, auditing code changes, or checking adherence to coding standards. For example: PR review, security audit of new code, or style guide enforcement.