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/projectsgit clone --depth 1 https://github.com/usathyan/epistractWhat 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.00019 | $0.00341 |
| Opus 5 | $0.00010 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
epistract-projects 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 2d 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
Manage the project registry — the map of named datasets to their directories, domains,
and creation dates ($EPISTRACT_HOME/registry.json, default ~/.epistract/).
Usage Guard
If invoked with no arguments or with --help: Display the following usage block verbatim and stop.
Usage: /epistract:projects <action> [options]
Actions:
list List all registered projects
info <name> Show a project's domain, root, and source count
delete <name> [--purge] Remove a project from the registry.
Without --purge, corpus files and pipeline outputs
are left untouched; with --purge the .epistract
state dir (manifest + index) is also removed.
Examples:
/epistract:projects list
/epistract:projects info glp1-research
/epistract:projects delete old-project --purge
PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m core.cli projects list
PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m core.cli projects info <name>
PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python3 -m core.cli projects delete <name> [--purge]
For list, present a table of name, domain, and root. Deletion is registry-only by
default; confirm before using --purge, which removes indexed state.
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.
- 2d ago First seen · 38 lines · 19 tokens per session scan A 693645aba507
epistract-projects is a command published in the GitHub repository usathyan/epistract (8 stars, last pushed 17d ago), licensed MIT. It adds 19 tokens to every session and 341 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
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.