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 skills/avibebuilder/claude-prime/docs-seekernpx skills add avibebuilder/claude-prime --skill docs-seekergit clone --depth 1 https://github.com/avibebuilder/claude-primeWrote 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/avibebuilder/claude-prime/docs-seeker)<a href="https://agentmods.dev/skills/avibebuilder/claude-prime/docs-seeker"><img src="https://agentmods.dev/badge/skills/avibebuilder/claude-prime/docs-seeker.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 | $0.00116 | $0.01223 |
| Opus 5 | $0.00058 | $0.00611 |
| Sonnet 5 | $0.00023 | $0.00245 |
| Haiku 4.5 | $0.00012 | $0.00122 |
Grade A, and why
docs-seeker 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Why fetch instead of recall
Trained knowledge rots. Library APIs rename fields, deprecate hooks, restructure auth flows, and change defaults between minor versions. Answering from memory is how you get confidently wrong code. Replace memory with retrieval — cheaply, from sources designed for AI consumption.
The source hierarchy (and why)
Prefer sources in this order. The ranking is about signal per token, not just availability.
-
llms.txton the official docs site — hand-curated by the project, AI-optimized, token-dense, always current. This is the ideal source when it exists. Try{official-docs-url}/llms.txtfirst for any library with a docs site; many projects ship one even if they don't advertise it. Ifllms.txtis just an index of links, follow the most relevant ones.llms-full.txtexists on some sites and contains the full corpus — only reach for it when the user explicitly wants comprehensive docs, since it's large. -
Context7 — a mirror that ingests GitHub repos and exposes them at
https://context7.com/{org}/{repo}/llms.txt, with optional?topic={keyword}filtering. Use this when the project has no officialllms.txt, or when you want to scope to one feature. The{org}/{repo}path mirrors GitHub exactly — derive it from the user'spackage.json, imports, lockfile, or the project's GitHub URL rather than guessing. For docs sites without a clear repo, Context7 also hostshttps://context7.com/websites/{normalized-path}/llms.txt. -
GitMCP — any GitHub repo is accessible by swapping
github.com→gitmcp.ioin the URL. Useful when Context7 doesn't have the repo indexed, or when you need source-of-truth README/examples straight from the repo. -
WebSearch — last resort. Slower, noisier, and you'll spend tokens filtering results. Only fall here when the three structured sources all miss. When you do search, query for
"{library} llms.txt"first — it often surfaces an official or community-maintained one.
On any 404, timeout, or empty response: move to the next tier immediately. Never retry a failed source.
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.
- 5d ago First seen · 53 lines · 116 tokens per session scan A 4657b09ccc8a
docs-seeker is a skill published in the GitHub repository avibebuilder/claude-prime (119 stars, last pushed 3mo ago), licensed MIT. It adds 116 tokens to every session and 1,223 once invoked, about $0.0006 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-30.
Other skills, from other repositories
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.