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.
git clone --depth 1 https://github.com/raintree-technology/docpullWrote 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/commands/raintree-technology/docpull/web-add)<a href="https://agentmods.dev/commands/raintree-technology/docpull/web-add"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-add/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.
<a href="https://agentmods.dev/commands/raintree-technology/docpull/web-add"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-add.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.00951 |
| Opus 5.5 | $0.00016 | $0.00380 |
| Sonnet 5.5 | $0.00008 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
web-add 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 1mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a web source to this session
The user wants to add a source to docpull's local Markdown index so it's searchable later via /web-search (or directly via the grep_docs MCP tool). This command is the web/source-facing name for the older /docs-add workflow.
User input: $ARGUMENTS
How to handle the input
Inspect $ARGUMENTS:
-
Empty or missing. Reply with a one-line usage hint and stop:
Usage: /web-add <alias>, /web-add <https-url>, or /web-add <name> <https-url>. Run /web-list to see what's already cached. -
One token, no URL scheme (e.g.
react,fastapi).- Treat as a built-in alias. Call
ensure_docs(source="<alias>"). The defaultragprofile is right for most cases - only override if the user mentioned a specific profile. - If the alias is unknown, the tool will return an error listing available aliases. In that case call
list_sources()and suggest the closest match by edit distance, or recommend running/web-add <name> <url>with the source URL.
- Treat as a built-in alias. Call
-
One token, an HTTPS URL (starts with
https://).- Call
list_sources()first so you can detect both built-in aliases and user-defined aliases, including sources that have not been fetched yet. - Auto-derive an alias name from the hostname:
- Take the hostname.
- Strip a leading
docs.orwww.if present. - Take the first dot-separated label.
- Lowercase it.
- Examples:
https://docs.fastapi.tiangolo.com->fastapi;https://nextjs.org/docs->nextjs;https://example.com/blog->example.
- If the derived name already appears in
list_sources(), tell the user and suggest the explicit/web-add <name> <url>form so they pick a unique name. Do not calladd_sourcefor a derived name that already exists. - Otherwise call
add_source(name=<derived>, url=<url>)to register, thenensure_docs(source=<derived>)to fetch.
- Call
-
Two tokens, second is an HTTPS URL (
<name> <url>).- Validate the name is a sensible alias (alnum +
_ . -, <=128 chars). If not, ask for a cleaner name. - Call
add_source(name=<name>, url=<url>). This intentionally updates an existing user-defined alias with the same name. If it returns "is a builtin source", tell the user thatadd_sourcerefuses to shadow builtins by default. Do not passforce=truewithout explicit user consent. - Then call
ensure_docs(source=<name>)to fetch.
- Validate the name is a sensible alias (alnum +
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.
- 1mo ago First seen · 56 lines · 41 tokens per session scan A 5d0c17dfeb3f
web-add is a command published in the GitHub repository raintree-technology/docpull (28 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 951 once invoked, about $0.0002 per session on Opus 5.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 commands, from other repositories
batch
This page documents how the livewiki batch command is registered with the Commander CLI framework and how it formats batch run reports for human consumption.
export
The livewiki export command turns the project's curated wiki into a deliverable artifact on disk: either a flattened snapshot under .livewiki/export/ / (for generic, github-wiki, and gitlab-wiki targets) or a synthesized repository-root README.md (for the readme target).
install
This page explains how the livewiki install CLI command detects installed coding agents and safely configures the livewiki MCP server entry, hook templates, shared skills, and optional pointer files.
pointer
This page documents the livewiki pointer subcommand, which manages an opt-in "pointer" block inside an AGENTS.md or CLAUDE.md file at the repository root.
index-cmd
The index command reindexes a repository and synchronizes its anchor ledger while selecting human-readable, JSON, or quiet output.
init
The livewiki init command is the CLI entry point that provisions a repository's livewiki directories, indexes the source tree, and (optionally) drives the full LLM documentation pipeline.