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-filesgit 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-files)<a href="https://agentmods.dev/commands/usathyan/epistract/add-files"><img src="https://agentmods.dev/badge/commands/usathyan/epistract/add-files.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.00024 | $0.00319 |
| Opus 5 | $0.00012 | $0.00160 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
epistract-add-files 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 4d 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
Copy one or more source documents into a project's corpus. Files are deduplicated by
sha256 content hash and recorded in the project manifest, which is what makes
/epistract:index incremental — re-indexing skips unchanged sources.
Usage Guard
If invoked with no arguments or with --help: Display the following usage block verbatim and stop.
Usage: /epistract:add-files <path>... [--project <name>]
Required:
<path>... One or more file paths to add to the corpus
Options:
--project <name> Target project (default: project detected from the current
directory, or $EPISTRACT_PROJECT)
Examples:
/epistract:add-files paper1.pdf paper2.pdf --project glp1-research
/epistract:add-files ~/downloads/*.pdf --project acme-contracts
Arguments
paths(required): One or more file paths.--project(optional): Target project name.
PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m core.cli add files <path>... [--project NAME]
Report how many files were added, how many were skipped as duplicates, and any missing
paths. Then suggest running /epistract:index <project> to extract and index the new documents.
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.
- 4d ago First seen · 39 lines · 24 tokens per session scan A 67aa02703b94
epistract-add-files is a command published in the GitHub repository usathyan/epistract (8 stars, last pushed 20d ago), licensed MIT. It adds 24 tokens to every session and 319 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.