docs-list

A command that lists source names and files already downloaded and cached locally for documentation searches.

In plain words
What is it for?
Use it before documentation searches to see cached sources, file counts, fetch age, and suggested refresh or search commands.
Why use it?
It shows what documentation is available without fetching anything, so you can tell whether a later search can use a local source. It also identifies sources that have not been refreshed recently.

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/raintree-technology/docpull/docs-list
Clone the repo
git clone --depth 1 https://github.com/raintree-technology/docpull
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 262 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.00013 $0.00262
Opus 5 $0.00006 $0.00131
Sonnet 5 $0.00003 $0.00052
Haiku 4.5 $0.00001 $0.00026

Measured yesterday against content hash 713d4950af42, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

plugin/commands/docs-list.md · 26 lines

What it actually says

List cached sources

Compatibility alias: prefer /web-list for new web-source workflows.

Show what's available to /docs-search right now.

Workflow

  1. Call list_indexed(). It returns source aliases that have been fetched, with file count and how long ago they were fetched.

  2. If empty: reply with a one-liner pointing to /docs-add and list_sources for the built-in alias list. Don't fetch anything.

  3. If non-empty: render the list as the tool returned it (it's already formatted). Note any sources marked stale (older than 7 days) and suggest /docs-refresh <source> for those if there are any.

  4. If the user is likely going to follow up with a search, suggest /docs-search <pattern> [source] once at the bottom.

Don't

  • Don't crawl, fetch, or call ensure_docs from this command. It's a read-only listing.
  • Don't expand each source's file tree — list_indexed summarizes for a reason.
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. yesterday First seen · 26 lines · 13 tokens per session scan A 713d4950af42

Subscribe to this mod's changes

docs-list is a command published in the GitHub repository raintree-technology/docpull (25 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 262 once invoked, about $0.0001 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.