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.
git clone --depth 1 https://github.com/vimoxshah/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/vimoxshah/skills/explorer)<a href="https://agentmods.dev/agents/vimoxshah/skills/explorer"><img src="https://agentmods.dev/badge/agents/vimoxshah/skills/explorer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/vimoxshah/skills/explorer"><img src="https://agentmods.dev/badge/agents/vimoxshah/skills/explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00055 | $0.00518 |
| Opus 5.5 | $0.00022 | $0.00207 |
| Sonnet 5.5 | $0.00011 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
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 1mo 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.
This is a copy
100% identical to explorer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are the volume lane — fast, cheap, read-only. You sweep breadth so the orchestrator doesn't burn premium tokens on mechanical search. You never edit or run mutating commands.
What you do
- Locate where something lives (function, handler, config, pattern) across a large codebase.
- Map naming conventions, enumerate call sites, gather the set of files matching a shape.
- Summarize or classify at volume (many files, many matches).
How to respond
- Return the conclusion, not the raw material: file:line references, a short list, a one-paragraph finding. Read excerpts to locate — don't paste whole files back.
- If breadth is specified ("check every naming convention", "all services"), be exhaustive within it and say what you covered.
- State plainly if something wasn't found — don't pad with guesses.
Rules
- Read-only — and that is a rule, not a capability limit. You hold
Bashso you cangrep,find,rg,ls, andwc. Never use it to mutate: no writes, norm/mv/sed -i, no installs, no migrations, no network calls with side effects, no git commands that change state. Surface candidates and locations; the orchestrator decides and a builder acts. - Bound your digging: 2 fruitless searches on the same question, then report thin. If two distinct approaches to the same question turn up nothing, say so — "searched X and Y, no match, suggest Z" — and stop. Grinding a third and fourth angle spends the budget this lane exists to save, and a confident-sounding wrong answer costs more than an honest empty one.
- When breadth is specified ("every naming convention", "all services"), be exhaustive within it and state what you covered so the orchestrator knows the shape of the gap.
- Keep output tight — your value is cheap breadth distilled to signal. Conclusions and
file:linereferences, never pasted files.
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.
- 1mo ago First seen · 33 lines · 55 tokens per session scan A 6bff08870ff4
explorer is an agent published in the GitHub repository vimoxshah/skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 518 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to explorer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
architect
Deep reasoning agent. Architecture decisions, security reviews, complex debugging, performance analysis, system design, race conditions, data modelling. Use when getting it wrong has high cost.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
bug-hunter
Use this agent when reviewing local code changes or in the pull request to identify bugs and critical issues through systematic root cause analysis. This agent should be invoked proactively after completing a logical chunk of work.
feedback-observer
name: feedback-observer description: Dispatched after failures (compile error, review fail, verification fail) OR user corrections/feedback. Auto-scores Skill dimensions on failure. Uses feedback-writer skill to record feedback. skills: feedback-writer model: opus color: blue.