index

A command that shows a visual summary of Beacon’s search index, including its stored chunks, file coverage, and data provider.

In plain words
What is it for?
Use it to check index size, coverage, sync time, and optionally list the files Beacon has indexed.
Why use it?
It gives you a quick view of whether the index is complete and up to date without displaying the whole dashboard as plain text.

Command

Install

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.

agentmods
npx agentmods add commands/sagarmk/beacon-plugin/index
Clone the repo
git clone --depth 1 https://github.com/sagarmk/beacon-plugin
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00160
Opus 5 $0.00010 $0.00080
Sonnet 5 $0.00004 $0.00032
Haiku 4.5 $0.00002 $0.00016

Measured 2d ago against content hash 77f72a31ef20, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

commands/index.md · 20 lines

What it actually says

/index

Run the command below. It outputs a colored dashboard with ANSI escape codes — the user sees it rendered in the command output section.

node ${CLAUDE_PLUGIN_ROOT}/scripts/index-info.js --pretty

After the command runs, add a one-line text summary extracted from the output, like:

Beacon index: 37 files, 99 chunks, 97% coverage, synced 4 minutes ago.

Do NOT re-display the full dashboard as text (ANSI codes render as garbage in markdown). If the command fails, suggest running /reindex.

Changes

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.

  1. 2d ago First seen · 20 lines · 20 tokens per session scan A 77f72a31ef20

Subscribe to this mod's changes

index is a command published in the GitHub repository sagarmk/beacon-plugin (43 stars, last pushed 12d ago), licensed MIT. It adds 20 tokens to every session and 160 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.