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/saski/arnesto/documentation-lookupnpx skills add saski/arnesto --skill documentation-lookupgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/documentation-lookup)<a href="https://agentmods.dev/skills/saski/arnesto/documentation-lookup"><img src="https://agentmods.dev/badge/skills/saski/arnesto/documentation-lookup.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.00050 | $0.00549 |
| Opus 5 | $0.00025 | $0.00275 |
| Sonnet 5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
documentation-lookup 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Lookup (Context7)
When a request depends on current library, framework, SDK, API, CLI, or cloud-service behavior, fetch current documentation through Context7 instead of relying on training data.
When to Use
Activate when the user:
- Asks setup or configuration questions.
- Requests code that depends on a library.
- Needs API or reference information.
- Names a framework, SDK, CLI, or cloud service whose behavior may have changed.
Do not use Context7 for refactoring, business-logic debugging, code review, scripts written from scratch, or general programming concepts that do not depend on current external documentation.
Workflow
Step 1: Choose the Transport
Prefer the Context7 MCP tools when they are available. Use the CLI only when the current harness does not expose the MCP tools.
Use no more than three Context7 resolution or documentation calls per question, regardless of transport.
Step 2: Resolve the Library ID
If the user did not provide a valid /org/project or /org/project/version ID:
- MCP: Call
resolve-library-idwith the official library name and the user's full question. - CLI fallback: Run
npx ctx7@latest library <name> "<user's question>".
Do not send API keys, passwords, credentials, or other secrets in the query.
Step 3: Select the Best Match
Choose one result using:
- Exact or closest official name match.
- Description relevance to the user's question.
- High or Medium source reputation when available.
- Higher benchmark score and useful snippet coverage.
- A version-specific ID when the user specified a version.
Step 4: Fetch the Documentation
- MCP: Call
query-docswith the selected library ID and the user's specific question. - CLI fallback: Run
npx ctx7@latest docs <libraryId> "<user's question>".
If a CLI request fails with a quota error, tell the user and suggest npx ctx7@latest login or CONTEXT7_API_KEY. If the answer remains unclear after the call limit, state the uncertainty instead of guessing.
What ships with it
1 file 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.
- 5d ago First seen · 62 lines · 50 tokens per session scan A 632f50f27279
documentation-lookup is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 9d ago), licensed Unlicense. It adds 50 tokens to every session and 549 once invoked, about $0.0003 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 skills, from other repositories
pixir-delegate
Use Pixir as a headless subagent runtime from Claude Code or any harness with skill ! preprocessing (Codex roots and other no-hydration hosts use pixir-delegate-codex instead) — one-shot workers (pixir --json), parallel fan-out to N children (pixir delegate --spec), resumable steering (pixir resume), evidence…
pixir-delegate-codex
Use when a Codex CLI/Desktop root should fan out subagents, delegate to Pixir workers, run parallel workers, or manage a resident delegation daemon via Pixir Delegate; covers Codex preflight, AGENTS.md, approvals/sandbox, dry-run, daemon start/status/attach/cancel, closure evidence, and audited single-run execution…
pixir-diagnostics
Diagnose Pixir and T3 Code Pixir incidents from local canonical evidence. Use when a Pixir run, ACP/T3 thread, subagent/workflow, provider replay, or daily-driver dogfood session appears stuck, inconsistent, missing tool output, or hard to classify.
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
pixir-delegate-native
Delegate work to subagents from INSIDE a Pixir session using the native Subagent tools (spawnagent, waitagent, closeagent, listagents, sendinput) instead of shelling out to the pixir CLI. Use when you are a Pixir session that needs to fan out parallel workers, steer a child, or run skill-backed workflow templates …
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.