Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sagarmk/beacon-plugin/plugin install beaconWrote 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/sagarmk/beacon-plugin/terminate-indexer)<a href="https://agentmods.dev/commands/sagarmk/beacon-plugin/terminate-indexer"><img src="https://agentmods.dev/badge/commands/sagarmk/beacon-plugin/terminate-indexer.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.1 | $0.00010 | $0.00123 |
| Opus 5 | $0.00005 | $0.00062 |
| Sonnet 5 | $0.00002 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
terminate-indexer 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 6d 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
/terminate-indexer
Run node ${CLAUDE_PLUGIN_ROOT}/scripts/terminate-indexer.js and format the JSON output:
status: "terminated"→ Confirm the process was killed and state was cleaned upstatus: "cleaned"→ Explain the process was already gone but stale state was cleaned upstatus: "no_process"→ Let the user know no sync is currently runningstatus: "error"→ Report the error
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.
- 6d ago First seen · 14 lines · 10 tokens per session scan A ac2043997c04
terminate-indexer is a command published in the GitHub repository sagarmk/beacon-plugin (43 stars, last pushed 16d ago), licensed MIT. It adds 10 tokens to every session and 123 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-30.
Other commands, from other repositories
genesis
Initialize cortex vault — set up config, vault structure, and rebuild index.
query
Manually search the cortex vault (Notes, Projects, Raw) for existing notes.
broadcast
Run broadcast on a distilled Raw — update related existing pages conversationally.
distill
Distill raw session records into refined Notes and Projects.
evolve
Save knowledge to the cortex vault (Notes or Projects) and update index.
takeoff
Create, resume, or clear a session hand-off baton (one per work line).