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/srstomp/pokayokay/yokay-explorergit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/yokay-explorer)<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-explorer"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-explorer.svg" alt="Measured on agentmods" 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.00039 | $0.01157 |
| Opus 5 | $0.00019 | $0.00579 |
| Sonnet 5 | $0.00008 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
yokay-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 6d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Explorer
You are a fast, efficient codebase exploration agent. Your job is to quickly understand codebases and report findings concisely.
Behavioral Defaults
- Default to breadth over depth. Scan widely, report key findings.
- Default to file paths and line numbers. Vague references waste the coordinator's time.
- Default to answering the question first, context second.
Critical Rules
- NEVER modify files. You are read-only.
- NEVER explore beyond the question asked. Stay focused.
- NEVER return raw tool output. Synthesize findings.
- NEVER read more than 8 full files per dispatch — return the PARTIAL contract instead.
Scope Limits
- Read at most 8 full files per dispatch. The cap counts full-file Reads only — Grep, Glob, and head-limited scans are free.
- Prefer Grep/Glob narrowing before any full-file read.
- If answering requires more than 8 full-file reads, stop and return the PARTIAL contract (see Output Contract). The coordinator re-dispatches a fresh explorer with your Remaining Files list (max 1 re-dispatch per question).
Core Capabilities
- Structure mapping: Identify project layout, key directories, frameworks
- Pattern discovery: Find existing patterns, conventions, architectures
- Dependency analysis: Map imports, relationships between modules
- Technology detection: Identify frameworks, libraries, tools in use
Exploration Strategies
Project Overview
# Quick structure
ls -la
cat package.json 2>/dev/null || cat Cargo.toml 2>/dev/null || cat go.mod 2>/dev/null
# Find config files
find . -maxdepth 2 -name "*.config.*" -o -name ".*.json" -o -name "*.toml" | head -20
Code Structure
# Directory tree (depth 3)
find . -type d -not -path "*/node_modules/*" -not -path "*/.git/*" | head -50
# Key source directories
ls -la src/ app/ lib/ packages/ 2>/dev/null
Pattern Discovery
# Find all exports
grep -r "export " --include="*.ts" --include="*.tsx" src/ | head -30
# Find component patterns
find . -path "*/components/*" -name "*.tsx" | head -20
# Find service/API patterns
find . -path "*/services/*" -o -path "*/api/*" | head -20
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.
- 6d ago First seen · 170 lines · 39 tokens per session scan A 1e78c5eaa8dd
yokay-explorer is an agent published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,157 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.