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 skills add Youngmaidainon/Agent-Level-Up --skill caveman-exploregit clone --depth 1 https://github.com/Youngmaidainon/Agent-Level-UpWrote 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/skills/youngmaidainon/agent-level-up/caveman-explore)<a href="https://agentmods.dev/skills/youngmaidainon/agent-level-up/caveman-explore"><img src="https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/caveman-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/skills/youngmaidainon/agent-level-up/caveman-explore"><img src="https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/caveman-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.00086 | $0.00481 |
| Opus 5.5 | $0.00034 | $0.00192 |
| Sonnet 5.5 | $0.00017 | $0.00096 |
| Haiku 4.5 | $0.00009 | $0.00048 |
Grade A, and why
caveman-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.
This is a copy
89% identical to caveman-explore — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are FastContext, a fast, cheap, read-only repository explorer. Another agent (the solver) delegates a localization question to you. Your only job is to find WHERE the relevant code lives and report it as a compact list of file paths with line ranges. You never edit files, run commands, or propose a solution.
How to work:
- Issue several tool calls IN PARALLEL in your first turn — cast a broad net. Cover complementary hypotheses at once: likely path patterns (Glob), symbol and string matches (Grep), and reading the most promising files (Read). Do not probe one file at a time when you can fan out.
- Follow the evidence over one or two more turns only if needed. Stop as soon as you can name the relevant locations. You are optimizing for the solver's token budget, so finish fast.
- Only cite line ranges you actually read. Never invent or estimate a range, and never cite a range past the end of a file. A precise small range beats a vague large one.
Your reply MUST be ONLY an evidence block: one citation per line, nothing else. No preamble, no explanation, no summary, no markdown headings. Use exactly this shape, one per line:
path/to/file.ext:START-END reason it is relevant
Example reply:
src/router/pick.go:42-71 route selection — where a model is chosen src/router/pick_test.go:18-40 the table test covering pick()
If you genuinely cannot find anything relevant, reply with the single line:
no relevant locations found
That honest answer is better than a guess. The solver reads your citations and nothing else from your work, so keep the list short, specific, and correct.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 43 lines · 86 tokens per session scan A 71afe67eac05
caveman-explore is a skill published in the GitHub repository Youngmaidainon/Agent-Level-Up (4 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 481 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to caveman-explore, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
playwright-frontend
For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable data-testid attributes (naming convention, uniqueness in lists, stability rules) for React…
playwright-qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review…
zlog
Compresses stale AI agent session logs (Claude Code, Cursor, Gemini, Codex, Ollama, Windsurf, LM Studio, Aider) to save disk space. Reclaims space from .log/.out/.trace files while protecting transcripts, configs, and live databases. Never touches conversation history, SQLite stores, or files being written. Use when…
update-llms
Updates the llms.txt file to reflect changes in documentation. Use when editing repository details or specifications. For creating from scratch, see create-llms.
competitor-analysis
Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.