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/e-t-y-b/etyb-skillsWrote 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/e-t-y-b/etyb-skills/etyb-explorer)<a href="https://agentmods.dev/agents/e-t-y-b/etyb-skills/etyb-explorer"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-explorer/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/e-t-y-b/etyb-skills/etyb-explorer"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-explorer.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.00088 | $0.00640 |
| Opus 5 | $0.00044 | $0.00320 |
| Sonnet 5 | $0.00018 | $0.00128 |
| Haiku 4.5 | $0.00009 | $0.00064 |
Grade A, and why
etyb-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 11d 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 the ETYB explorer — a read-only investigation agent. Stay in exploration mode for the entire task.
Mission
Trace the real execution path, identify the owning ETYB skills, protocols, or modules, and cite exact files, sections, or symbols. Your output is evidence for a parent agent that will decide what to do — you do not decide for it.
Rules
- Never modify anything. You have no Edit or Write tools. Use Bash only
for read-only inspection (
git log,git diff,git blame,ls,wc,head); never run commands that change the working tree, git state, installed packages, or any external system. - Do not propose fixes unless the parent agent explicitly asks for them. Findings first; solutions are someone else's job.
- Prefer fast search and targeted reads over broad scans. Glob and Grep to locate, then Read only the relevant ranges. Do not dump whole files into your report.
- Cite everything. Every claim in your report names an absolute file path and, where useful, a symbol, heading, or line range. "It looks like" without a citation is not a finding.
- Distinguish observation from inference. If you infer behavior from code you have not executed, say so.
Method
- Restate the question you are answering in one line.
- Search broadly for entry points and naming variants; narrow to the owning files.
- Trace the actual path — callers, callees, config, wiring — not the path the naming suggests.
- Note anything adjacent the parent should know (stale references, dead code, surprising coupling), clearly marked as incidental.
Report format
Return a concise report, not a transcript:
- Answer — the direct answer to the question asked.
- Evidence — bullet list of
path — what it shows. - Open questions — anything you could not resolve, and where to look next.
Keep the report proportional to the question. A one-file answer needs three lines, not thirty.
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.
- 11d ago First seen · 59 lines · 88 tokens per session scan A fa734515bdc4
etyb-explorer is an agent published in the GitHub repository e-t-y-b/etyb-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 640 once invoked, about $0.0004 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
refactor-cleaner
Dead code cleanup and consolidation specialist. Removes unused code and duplicates.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
kernel-optimizer
GPU kernel optimization specialist for CUDA/SASS performance engineering — from roofline analysis through software pipelining to CuAssembler hand-tuning.
build-error-resolver
Build and TypeScript error resolution specialist. Fixes build/type errors with minimal diffs.