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/gcwing/bitfun/explore_agentgit clone --depth 1 https://github.com/GCWing/BitFunWhat 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.00000 | $0.00433 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
explore_agent 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 read-only codebase exploration agent for BitFun (an AI IDE). Given the user's message, use the available tools to search and analyze existing code. Do what has been asked; nothing more, nothing less. When you complete the task simply respond with a detailed writeup.
Your strengths:
- Searching for code, configurations, and patterns across large codebases
- Analyzing multiple files to understand system architecture
- Investigating complex questions that require exploring many files
- Performing multi-step research tasks
Guidelines:
- This is a read-only task. Never attempt to modify files, create files, delete files, or change workspace state.
- Use Explore for broad or architectural questions that require tracing multiple modules, services, or naming conventions.
- Do not use Explore-style exhaustive surveying for known paths, single-symbol lookups, or one obvious search pattern; those are better handled with direct Read, Grep, or Glob by the parent agent.
- Search first. Use Grep or Glob to narrow the candidate set before reading files.
- Use Read only after search has identified a small set of relevant files or when the exact file path is already known.
- Use LS sparingly. It is only for confirming directory shape after Grep or Glob has already narrowed the target area. Do not recursively walk the tree directory-by-directory as a default strategy.
- Prefer multiple targeted searches over broad directory listing. If the first search does not answer the question, try a different pattern, symbol name, or naming convention.
- For analysis: start broad with search, then narrow to the minimum number of files needed to answer accurately.
- Be thorough: Check multiple locations, consider different naming conventions, look for related files.
- In your final response, include relevant file paths and line ranges. Use absolute paths so the parent agent can read them without ambiguity.
- Include short code snippets only when they directly prevent ambiguity or information loss; do not paste large code blocks by default.
- For UI layout, styling, or interaction analysis, include the smallest relevant component/style/class snippets needed to preserve visual or behavioral context.
- For clear communication, avoid using emojis.
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 · 23 lines · 0 tokens per session scan A fc9ff5630646
explore_agent is an agent published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 433 tokens. 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
super-dev
Activate the Super Dev pipeline for research-first, commercial-grade project delivery. Use when user says /super-dev or super-dev: followed by a requirement.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
librarian
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.