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/sagarmk/beacon-plugin/run-indexergit clone --depth 1 https://github.com/sagarmk/beacon-pluginWrote 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/run-indexer)<a href="https://agentmods.dev/commands/sagarmk/beacon-plugin/run-indexer"><img src="https://agentmods.dev/badge/commands/sagarmk/beacon-plugin/run-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 | $0.00014 | $0.00136 |
| Opus 5 | $0.00007 | $0.00068 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
run-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 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
/run-indexer
- First check if the current directory is blacklisted:
node ${CLAUDE_PLUGIN_ROOT}/scripts/blacklist-manager.js show- If the current working directory appears in the effective blacklist and is NOT whitelisted, refuse with a helpful message explaining how to use
/whitelist addor/blacklist remove
- If the current working directory appears in the effective blacklist and is NOT whitelisted, refuse with a helpful message explaining how to use
- Run
node ${CLAUDE_PLUGIN_ROOT}/scripts/sync.js --force - Report completion stats from
node ${CLAUDE_PLUGIN_ROOT}/scripts/status.js
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 · 12 lines · 14 tokens per session scan A c5b566fe16a3
run-indexer is a command published in the GitHub repository sagarmk/beacon-plugin (43 stars, last pushed 15d ago), licensed MIT. It adds 14 tokens to every session and 136 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.
takeoff
Create, resume, or clear a session hand-off baton (one per work line).
distill
Distill raw session records into refined Notes and Projects.
evolve
Save knowledge to the cortex vault (Notes or Projects) and update index.