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/s1lv4/th0th/indexgit clone --depth 1 https://github.com/S1LV4/th0thWrote 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/s1lv4/th0th/index)<a href="https://agentmods.dev/commands/s1lv4/th0th/index"><img src="https://agentmods.dev/badge/commands/s1lv4/th0th/index.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.00009 | $0.00300 |
| Opus 5 | $0.00005 | $0.00150 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
index 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
Kick off a th0th indexing job for the current directory.
Steps:
- Run
pwdto get the absolute path of the current working directory. - Determine
projectId:- If the user passed
$1, use it as projectId. - Otherwise use the basename of the directory (last path segment).
- If the user passed
- Call
mcp__th0th__th0th_index_projectwithprojectPath=<pwd>,projectId=<chosen>, andforceReindex=trueonly if the user explicitly asked to force. - Get the
jobIdback and pollmcp__th0th__th0th_index_statuswith that jobId every ~10 seconds until status isindexedorerror. - Report progress succinctly: percentage, ETA, fileProcessed counters when available. Do not spam.
- On completion, show a one-line summary:
Indexed <projectId>: <files> files / <chunks> chunks / <duration>.
Never re-trigger indexing if there's already an in-flight job for the same projectId (check via th0th_list_projects first).
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 · 20 lines · 9 tokens per session scan A d90b4e88c38c
index is a command published in the GitHub repository S1LV4/th0th (135 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 300 once invoked, about $0.0000 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-30.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.