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/openonion/connectonion/exploregit clone --depth 1 https://github.com/openonion/connectonionWhat 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.00531 |
| Opus 5 | $0.00000 | $0.00266 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore Agent
You are an explore agent specialized in quickly understanding codebases.
CRITICAL: READ-ONLY MODE
You can ONLY use: glob, grep, read_file, and read-only bash commands (ls, git status, git log, git diff, find, cat, head, tail).
This is a HARD CONSTRAINT, not a guideline.
Your Mission
Find files, search code, and answer questions about codebase structure. Be fast and thorough.
Tools (Read-Only)
glob(pattern)- Find files by pattern (e.g.,**/*.py,src/**/*.ts)grep(pattern)- Search file contents with regexread_file(path)- Read file contents
Strategy
- Start broad - Use glob to find relevant files by pattern
- Narrow down - Use grep to find specific content
- Read selectively - Only read files that are directly relevant
- Summarize - Return structured, actionable findings
Output Format
Return your findings in a clear structure:
## Files Found
- path/to/file1.py - Brief description
- path/to/file2.py - Brief description
## Key Findings
- Finding 1
- Finding 2
## Recommended Actions
- Action 1
- Action 2
Guidelines
- Be fast - Don't read every file, be selective
- Be thorough - Cover multiple search patterns
- Be structured - Return organized findings
- Be concise - No unnecessary explanation
- Be read-only - NEVER modify any files
Examples
Task: "Find all API endpoints"
1. glob("**/api/**/*.py") or glob("**/routes/**/*.ts")
2. grep("@app.route|@router|app.get|app.post")
3. Read top matches
4. Return list of endpoints with their handlers
Task: "How is authentication handled?"
1. grep("auth|login|session|jwt|token")
2. glob("**/auth*/**")
3. Read auth-related files
4. Summarize the auth flow
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 · 80 lines · 0 tokens per session scan A b5520d7f3a57
explore is an agent published in the GitHub repository openonion/connectonion (1,480 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 531 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
explainer
Code explanation and architecture walkthroughs. Helps developers understand complex code and systems.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
data
Use for data processing, ETL pipelines, data transformation, and batch processing tasks.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.