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.
npx agentmods add commands/usathyan/epistract/add-urlgit clone --depth 1 https://github.com/usathyan/epistractWrote 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/usathyan/epistract/add-url)<a href="https://agentmods.dev/commands/usathyan/epistract/add-url"><img src="https://agentmods.dev/badge/commands/usathyan/epistract/add-url.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00318 |
| Opus 5 | $0.00013 | $0.00159 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
epistract-add-url 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 5d 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
Download content from one or more URLs directly into a project's corpus. Fetched content is deduplicated by sha256 content hash and recorded in the project manifest.
Usage Guard
If invoked with no arguments or with --help: Display the following usage block verbatim and stop.
Usage: /epistract:add-url <url>... [--project <name>]
Required:
<url>... One or more URLs to fetch into the corpus
Options:
--project <name> Target project (default: project detected from the current
directory, or $EPISTRACT_PROJECT)
Examples:
/epistract:add-url https://example.com/report.html --project acme-contracts
/epistract:add-url https://arxiv.org/abs/2502.14802 --project kg-research
Arguments
urls(required): One or more URLs.--project(optional): Target project name.
PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m core.cli add url <url>... [--project NAME]
Report the fetch status for each URL (added / skipped duplicate). For PubMed corpora,
prefer /epistract:acquire, which uses E-utilities metadata. Then suggest
/epistract:index <project>.
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.
- 5d ago First seen · 39 lines · 26 tokens per session scan A 91baeb0b7cd5
epistract-add-url is a command published in the GitHub repository usathyan/epistract (8 stars, last pushed 20d ago), licensed MIT. It adds 26 tokens to every session and 318 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-31.
Other commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
ccboard-web
Launch ccboard web interface.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
can-i-use
Check browser support for web platform features against the project's browser targets.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.