fetch-docs

A command that looks up current documentation for a software library or framework through Context7, including the requested version and topic.

In plain words
What is it for?
Use it to check library APIs, confirm version-specific usage, research a framework feature, and apply the findings to a coding task.
Why use it?
It reduces mistakes caused by outdated or mismatched documentation when generating code. It also helps distinguish official guidance from community examples and identify deprecated or experimental APIs.

Command

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.

agentmods
npx agentmods add commands/aegntic/cldcde/fetch-docs
Clone the repo
git clone --depth 1 https://github.com/aegntic/cldcde
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 141 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00000 $0.00141
Opus 5 $0.00000 $0.00071
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

Measured 2d ago against content hash 8755e873ed42, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fetch-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 2d 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.

plugins/context7-docs/commands/fetch-docs.md · 30 lines

What it actually says

Fetch up-to-date library documentation via Context7 to ensure accurate code generation.

Steps

  1. Identify the library or framework the user needs docs for:
  2. Resolve the library ID using Context7:
  3. Query the documentation:
  4. Present the documentation in a usable format:
  5. Apply the documentation to the current task:
  6. Cache the result to avoid redundant lookups.

Format

Library: <name>@<version>
Source: Context7
Topic: <what was looked up>
Key APIs:

Rules

  • Always verify the documentation version matches the installed version.
  • Prefer official documentation over community examples.
  • Note any APIs marked as experimental or deprecated.
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. 2d ago First seen · 30 lines · 0 tokens per session scan A 8755e873ed42

Subscribe to this mod's changes

fetch-docs is a command published in the GitHub repository aegntic/cldcde (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 141 tokens. 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.