docs-lookup

A research agent that checks documents against multiple sources, including official API references and working examples.

In plain words
What is it for?
Use it to fact-check reports, verify API signatures and deprecations, and find examples from official documentation.
Why use it?
It helps prevent inaccurate technical details, outdated API information, and unsupported claims in generated documents.

Agent

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 agents/lehidalgo/codi/docs-lookup
Clone the repo
git clone --depth 1 https://github.com/lehidalgo/codi
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 130 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.00130
Opus 5 $0.00000 $0.00065
Sonnet 5 $0.00000 $0.00026
Haiku 4.5 $0.00000 $0.00013

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

Security

Grade A, and why

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

src/templates/skills/content-factory/agents/docs-lookup.md · 20 lines

What it actually says

Agent: codi-docs-lookup

Research agent for verifying content accuracy during document generation.

When to Delegate

  • Document generation needs fact-checking or API reference verification
  • The user wants to include accurate technical details in reports
  • Research is needed to support document content with real data

How to Use

Defined at .codi/agents/codi-docs-lookup.md. Invoke via the Agent tool with subagent_type set to codi-docs-lookup.

Key Capabilities

  • Multi-source documentation search
  • API signature and deprecation verification
  • Working example discovery from official sources
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 · 20 lines · 0 tokens per session scan A 53ab0085f476

Subscribe to this mod's changes

docs-lookup is an agent published in the GitHub repository lehidalgo/codi (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 130 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-31.