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-remove)<a href="https://agentmods.dev/commands/raintree-technology/docpull/web-remove"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-remove/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-remove"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-remove.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.00017 | $0.00460 |
| Opus 5.5 | $0.00007 | $0.00184 |
| Sonnet 5.5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade C, and why
web-remove scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Don't run `rm -rf` via Bash; the MCP tool's `delete_cache=true` does the safe path-validated deletion. This is a copy
92% identical to docs-remove — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Remove a web source
The user wants to remove a previously-added source. By default this also deletes cached Markdown to free disk and avoid stale answers.
User input: $ARGUMENTS
How to handle the input
Parse $ARGUMENTS as:
- First token = source alias (the alias to remove).
- Optional
--keep-cacheflag = remove the alias from the user registry but leave the cached.mdfiles on disk.
If empty: reply Usage: /web-remove <source> [--keep-cache]. Run /web-list to see what's cached. and stop.
Workflow
-
Default (no flag): remove alias AND delete cache. Call
remove_source(name=<source>, delete_cache=true). The MCP tool refuses to remove builtins (react,nextjs, etc.) - pass that error through to the user with the suggestion in step 3. -
--keep-cacheflag: remove alias only. Callremove_source(name=<source>, delete_cache=false). The cached Markdown stays;/web-search <source>will keep working until the user runs this without the flag. -
If the tool returns "is a builtin source": Tell the user that builtins can't be removed but they can be shadowed with a custom URL via
/web-add(or by editingsources.yamldirectly). -
If the tool returns the no-op response (no user source AND no cache to delete): tell the user there was nothing to remove. Don't error.
Output
One line: confirm what was removed (alias only, cache only, both, or nothing). The MCP tool's response is already specific - relay it.
Don't
- Don't run
rm -rfvia Bash; the MCP tool'sdelete_cache=truedoes the safe path-validated deletion. - Don't call this on builtins thinking force will help - there's no force flag for removal by design.
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 · 43 lines · 17 tokens per session scan C 1c9eb5cdd700
web-remove is a command published in the GitHub repository raintree-technology/docpull (28 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 460 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 92% identical to docs-remove, differing in 18 lines, and is treated as a copy.
Other commands, from other repositories
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.
verify
This page documents the livewiki verify CLI subcommand, which checks a generated wiki for the kinds of corruption that would break readers or CI pipelines.
serve
The livewiki serve command registers an MCP server on stdio inside the livewiki CLI, sharing the same runtime as the standalone livewiki-mcp binary.