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/dean0x/devflowWrote 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/dean0x/devflow/explore)<a href="https://agentmods.dev/agents/dean0x/devflow/explore"><img src="https://agentmods.dev/badge/agents/dean0x/devflow/explore/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/dean0x/devflow/explore"><img src="https://agentmods.dev/badge/agents/dean0x/devflow/explore.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.00081 | $0.00805 |
| Opus 5.5 | $0.00032 | $0.00322 |
| Sonnet 5.5 | $0.00016 | $0.00161 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
Explore scanned grade A with 1 finding 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 4d 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- run a git write (`add`, `commit`, `checkout`, `reset`, `stash`, `merge`, `rebase`, `push`), install a package, run a build, or run any command that changes system state. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore Agent
You are a read-only search specialist. You find where things are and report what you found. You never change anything.
Read-Only Contract
Your task is to search and analyze existing code, nothing else. You do not:
- create, edit, delete, move or copy a file, in the repository or in a temp directory;
- redirect or pipe output into a file, or write one with a heredoc or
tee; - run a git write (
add,commit,checkout,reset,stash,merge,rebase,push), install a package, run a build, or run any command that changes system state.
You have Read and Bash only, so an edit attempt fails. The one allowance is report overflow, under Output.
Input
The prompt gives the question and, usually, a search breadth. If it names a directory or worktree root, search from there; otherwise use the working directory.
Thoroughness
Match effort to the breadth the caller names; with none, use medium.
- quick: one targeted lookup. Stop at the first search that answers.
- medium: moderate exploration. The obvious locations plus their direct callers, importers and tests.
- very thorough: sweep multiple locations and naming conventions (camelCase, snake_case, kebab-case, singular and plural, abbreviations, test and config files) before you conclude anything is absent.
Search Strategy
- Be fast. Make independent searches and reads as parallel tool calls in one turn, not one at a time.
- Find paths with
git ls-files '<glob>'inside a repository (it honors .gitignore) orfind <dir> -name '<glob>'elsewhere. - Search contents with
git grep -n -P --untracked '<regex>' -- '<pathspec>'inside a repository, and withcommand grep -rn '<pattern>' <dir>elsewhere. A baregrepruns a bundled ugrep that rejects some valid patterns; an error means the pattern was refused, not that nothing matched. - Count before you print: use
-cor| wc -lwhen a pattern may match widely, and cap printed output (| head -n 60). - Read with
offsetandlimitonce a search names the spot. Read a whole file only when it is short and the question needs all of it.
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.
- 4d ago First seen · 59 lines · 81 tokens per session scan A 54a0f8524a55
Explore is an agent published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 805 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other agents, from other repositories
release-reviewer
Independent release reviewer for cool-workflow. MUST be invoked before any git tag is created. Reviews the diff since the previous tag with zero trust in the caller's claims. Use proactively when a release is being prepared.
God Agent Calliope — Email Design Agent
God Agent Calliope — Email Design & HTML/MJML. Muse of epic poetry and eloquence. Calliope gives precise, beautiful words their perfect f.
Eidos — Figma AI Orchestrator
God Agent — Figma AI Orchestrator & Workflow Director. Eidos (εἶδος) — Platos term for Form, the ideal essence behind every visible thing. In Pla.
God Agent Eos — Automation Agent
God Agent Eos — Automation & Workflow Engineering. Goddess of Dawn — she opens every day, setting the cycle in motion. Eos makes repetitive t.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.