documentation-lookup

documentation-lookup is a skill for Codex from Fmarzochi/EGC. It costs 51 tokens per session (1,142 once invoked), scanned A, a copy of documentation-lookup, Apache-2.0.

A guide for finding current documentation and examples for software libraries, frameworks, and programming interfaces.

In plain words
What is it for?
Use it when configuring tools such as React, Next.js, Prisma, or Supabase, or when looking up their methods and usage.
Why use it?
It reduces reliance on outdated knowledge when setup steps or API behavior may have changed.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

Good fit Use it when configuring tools such as React, Next.js, Prisma, or Supabase, or when looking up their methods and usage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fmarzochi/egc/documentation-lookup
Install

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.

Any agent
npx skills add Fmarzochi/EGC --skill documentation-lookup
Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

Made for: Codex.

Wrote 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.

agentmods badge for documentation-lookup

README.md
[![agentmods](https://agentmods.dev/badge/skills/fmarzochi/egc/documentation-lookup/github.svg)](https://agentmods.dev/skills/fmarzochi/egc/documentation-lookup)
Your own site
<a href="https://agentmods.dev/skills/fmarzochi/egc/documentation-lookup"><img src="https://agentmods.dev/badge/skills/fmarzochi/egc/documentation-lookup/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.

agentmods 80×15 button for documentation-lookup

Your own site · 80×15
<a href="https://agentmods.dev/skills/fmarzochi/egc/documentation-lookup"><img src="https://agentmods.dev/badge/skills/fmarzochi/egc/documentation-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01142
Opus 5 $0.00026 $0.00571
Sonnet 5 $0.00010 $0.00228
Haiku 4.5 $0.00005 $0.00114

Measured 9d ago against content hash 00cec6c12103, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 9d 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.

Origin

This is a copy

94% identical to documentation-lookup — 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.

.agents/skills/documentation-lookup/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Lookup (Context7)

When the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools resolve-library-id and query-docs) instead of relying on training data.

Core Concepts

  • Context7: MCP server that exposes live documentation; use it instead of training data for libraries and APIs.
  • resolve-library-id: Returns Context7-compatible library IDs (e.g. /vercel/next.js) from a library name and query.
  • query-docs: Fetches documentation and code snippets for a given library ID and question. Always call resolve-library-id first to get a valid library ID.

When to use

Activate when the user:

  • Asks setup or configuration questions (e.g. "How do I configure Next.js middleware?")
  • Requests code that depends on a library ("Write a Prisma query for...")
  • Needs API or reference information ("What are the Supabase auth methods?")
  • Mentions specific frameworks or libraries (React, Vue, Svelte, Express, Tailwind, Prisma, Supabase, etc.)

Use this skill whenever the request depends on accurate, up-to-date behavior of a library, framework, or API. Applies across harnesses that have the Context7 MCP configured (e.g. Gemini Code, Cursor, Codex).

How it works

Step 1: Resolve the Library ID

Call the resolve-library-id MCP tool with:

  • libraryName: The library or product name taken from the user's question (e.g. Next.js, Prisma, Supabase).
  • query: The user's full question. This improves relevance ranking of results.

You must obtain a Context7-compatible library ID (format /org/project or /org/project/version) before querying docs. Do not call query-docs without a valid library ID from this step.

Step 2: Select the Best Match

From the resolution results, choose one result using:

  • Name match: Prefer exact or closest match to what the user asked for.
  • Benchmark score: Higher scores indicate better documentation quality (100 is highest).
  • Source reputation: Prefer High or Medium reputation when available.
  • Version: If the user specified a version (e.g. "React 19", "Next.js 15"), prefer a version-specific library ID if listed (e.g. /org/project/v1.2.0).

Read the full file on GitHub · 90 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 90 lines · 51 tokens per session scan A 00cec6c12103

Subscribe to this mod's changes

documentation-lookup is a skill published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 1,142 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to documentation-lookup, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories