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-refresh)<a href="https://agentmods.dev/commands/raintree-technology/docpull/web-refresh"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-refresh/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-refresh"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-refresh.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.00021 | $0.00365 |
| Opus 5.5 | $0.00008 | $0.00146 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
web-refresh 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.
What it actually says
Refresh a cached web source
Force-refetch a source that's already cached. The default ensure_docs honors a 7-day cache; this command bypasses it.
User input: $ARGUMENTS
Workflow
-
Parse
$ARGUMENTSas a single source alias. If empty: replyUsage: /web-refresh <source>. Run /web-list to see what's cached.and stop. -
Call
ensure_docs(source=<source>, force=true). The tool will re-crawl the source (using whatever URL the alias resolves to) and overwrite the cached.mdfiles in place. -
If the alias is unknown: pass through the tool's error. Suggest
/web-add <source>if it's a built-in or/web-add <name> <url>if not. -
After success, report a one-line summary using the tool's response (pages fetched / skipped / failed).
When to use this vs /web-add
/web-add <name>- first time fetching, or when the cache is fresh and you want to use it./web-refresh <name>- already cached but you want the latest. Don't run this every time you search; the conditional-GET cache makes it cheap, but it still hits the network for every page.
Don't
- Don't loop this across all cached sources unprompted. If the user wants a global refresh, ask first.
- Don't pass
force=truetoensure_docsfrom any other command - that's what this command is for.
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 · 32 lines · 21 tokens per session scan A 66b1ee4bd08a
web-refresh is a command published in the GitHub repository raintree-technology/docpull (28 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 365 once invoked, about $0.0001 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.