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 alexei-led/cc-thingz --skill looking-up-docsgit clone --depth 1 https://github.com/alexei-led/cc-thingzWrote 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/alexei-led/cc-thingz/looking-up-docs)<a href="https://agentmods.dev/skills/alexei-led/cc-thingz/looking-up-docs"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/looking-up-docs.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.00115 | $0.01063 |
| Opus 5 | $0.00057 | $0.00531 |
| Sonnet 5 | $0.00023 | $0.00213 |
| Haiku 4.5 | $0.00012 | $0.00106 |
Grade A, and why
looking-up-docs 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 8d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Lookup
Get grounded, version-correct docs for a library, framework, CLI, or API. Never answer syntax or API questions from memory when lookup tools are available.
Scope
Use this skill for:
- API signatures, options, config keys, syntax, and examples.
- Versioned API behavior of a known library, framework, language, CLI, or standard library when the question is how to call or configure it.
- Context7 docs lookup, including explicit
ctx7,Context7, or/org/projectlibrary-ID requests. - Confirming versioned API behavior before writing code against an external API.
Do not use this skill for:
- Comparisons, recommendations, market research, current-state questions,
release-behavior questions, or best-practice surveys; route to
researching-web. - Repo-specific questions; search local files first.
- External queries containing secrets, credentials, personal data, private payloads, or proprietary code.
Reference Files
Read only what the question needs:
references/context7-cli.md— Context7 lookup commands, selection rules, limits, and fallbacks.references/official-sources.md— primary docs and registries by ecosystem.references/web-tools.md— platform web tools, query templates, and source quality rules.
Lookup Chain
Run tiers in order. Stop at the first tier that yields a grounded answer. State which tier produced the answer and whether fallback was used.
Tier 0 — Identify Package and Version
Find the exact package, module, CLI, language version, or framework version from local evidence.
If no local version is available, state version unknown and prefer latest
stable official docs. Do not invent a version.
Tier 1 — Context7
Use references/context7-cli.md for Context7 library resolution and docs fetch.
Best fit: versioned library and framework docs.
Escalate when Context7 is unavailable, rate-limited, returns no useful match after one rephrase and one alternate library name, or returns docs for the wrong version.
What ships with it
4 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.
- 8d ago First seen · 119 lines · 115 tokens per session scan A 65355e27fcb3
looking-up-docs is a skill published in the GitHub repository alexei-led/cc-thingz (35 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 1,063 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
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
mobile-flows-maestro
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory…
validate-api
Run the project's Hurl scenarios with an OIDC access token passed as a secret variable.
validate-mobile
Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence.
backend-architecture
This skill should be used for consequential backend architecture decisions: module or service boundaries; modular monoliths versus independent services; service extraction and data migration; data ownership and consistency; synchronous, event-driven, actor/stateful, or pipeline designs; failure isolation…
swiftui-expert
This skill should be used when SwiftUI work requires judgment about Observation and state ownership, view identity or lifecycle, navigation, app-target concurrency, persistence, Apple-platform behavior, accessibility, performance, or architecture. Trigger on "review this SwiftUI screen", "why isn't this view…