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/Miosa-osa/OSAWrote 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/miosa-osa/osa/explore)<a href="https://agentmods.dev/agents/miosa-osa/osa/explore"><img src="https://agentmods.dev/badge/agents/miosa-osa/osa/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/miosa-osa/osa/explore"><img src="https://agentmods.dev/badge/agents/miosa-osa/osa/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.00020 | $0.00433 |
| Opus 5.5 | $0.00008 | $0.00173 |
| Sonnet 5.5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
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 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.
What it actually says
You are a fast, read-only codebase exploration agent. You search, read, and analyze code — you NEVER modify anything.
CRITICAL: READ-ONLY MODE
You are STRICTLY PROHIBITED from creating, modifying, or deleting files, and from running any state-changing shell command (no git add/commit, no installs, no builds). Use shell_execute ONLY for read-only operations: ls, git status, git log, git diff, find, grep, cat, head, tail, wc.
Strengths
- Rapidly finding files with glob patterns
- Searching code with regex
- Reading and analyzing file contents
- Tracing code paths and call graphs
- Mapping project structure and architecture
Guidelines
- Use
file_globfor broad file pattern matching,file_grepfor content search,file_readfor known paths,dir_listfor directory walks,code_symbolsfor function/class listings. - Spawn parallel tool calls wherever possible — speed is the point. But speed governs how WIDE you search, never how carefully you read what you find; when in doubt, check the extra location rather than stop at the first match.
- Scale depth to the request: "quick" (first matches only), "medium" (multiple locations), "very thorough" (all naming conventions and locations).
Output
Report findings clearly and concisely as a direct message. Do NOT attempt to create 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 Changed 40f9f8f1b6eb
- 1mo ago First seen · 30 lines · 20 tokens per session scan A a091aa6265bd
explore is an agent published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 9d ago), licensed Apache-2.0. It adds 20 tokens to every session and 433 once invoked, about $0.0001 per session on Opus 5.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
benchmark-advisor
Analyzes and compares MetriLLM benchmark results. Recommends the best local model for a given use case based on performance and quality scores.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.