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/configgit clone --depth 1 https://github.com/sagarmk/beacon-pluginWhat 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.00012 | $0.00804 |
| Opus 5 | $0.00006 | $0.00402 |
| Sonnet 5 | $0.00002 | $0.00161 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
config 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/config
Manage Beacon plugin configuration. All changes are saved to the repo-local .claude/beacon.json override file.
Routing
Parse $ARGUMENTS to determine the subcommand:
- Empty or
show→ Show set <key> <value>→ Setproviderorprovider <name>→ Providerresetorreset <section>→ Reset
Show (default)
- Run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/config-manager.js show - Format the JSON output as a readable config overview:
- Show the active provider prominently at the top:
Provider: ollama (local)orProvider: custom - Group settings by section: Embedding, Chunking, Indexing, Search, Storage
- For each setting, show the key, value, and mark
[override]if source is"user"— leave unmarked if default - For array values (include/exclude patterns), show as a compact comma-separated list
- At the bottom, list available providers:
Available: ollama, openai, voyage, litellm - Keep total output under 30 lines
- Show the active provider prominently at the top:
Set
- Run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/config-manager.js set <key> <value> - If the script exits with an error (JSON on stderr), show the error message. If it's an unknown key, show the list of valid keys.
- If
dimensions_changedistruein the output:- ⚠️ Warn: "Changing dimensions from
<old>to<new>makes existing embeddings incompatible." - Ask: "Run
/reindexnow to rebuild the index?" - If the user confirms, delete the DB file (
rm -f .claude/.beacon/embeddings.db) and runnode ${CLAUDE_PLUGIN_ROOT}/scripts/sync.js
- ⚠️ Warn: "Changing dimensions from
- Otherwise, confirm:
Set search.similarity_threshold → 0.5
Provider
- Run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/config-manager.js provider <name> - If no name given, the script lists available providers — format them as a table with name, description, model, and dimensions.
- If the provider is not found, show the error with available provider names.
- If successful, show what was applied: model, endpoint, dimensions.
- If
api_key_envis not empty/none, remind: "Make sureOPENAI_API_KEYis set in your environment." - If
dimensions_changedistrue:- ⚠️ Warn: "Switching from
<old>to<new>dimensions. Existing embeddings are incompatible." - Ask: "Run
/reindexnow to rebuild the index with the new provider?" - If the user confirms, delete the DB and run sync.
- ⚠️ Warn: "Switching from
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 · 68 lines · 12 tokens per session scan A 3d02d1c34bfe
config is a command published in the GitHub repository sagarmk/beacon-plugin (43 stars, last pushed 12d ago), licensed MIT. It adds 12 tokens to every session and 804 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
rp-build-cli
Build with rp-cli context builder → chat → implement.
rp-investigate-cli
Deep codebase investigation and architecture research with rp-cli commands.
rp-oracle-export-cli
Export context for oracle consultation using rp-cli.
rp-reminder-cli
Continue your current workflow using rp-cli instead of built-in alternatives.
call-graph
Trace callers, callees, or paths using the call graph.
peek
Quickly find likely code locations without returning full code.