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/blacklistgit 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.00010 | $0.00273 |
| Opus 5 | $0.00005 | $0.00137 |
| Sonnet 5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
blacklist 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 3d 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
/blacklist
Parse the user's arguments and run the appropriate subcommand:
/blacklist(no args) →node ${CLAUDE_PLUGIN_ROOT}/scripts/blacklist-manager.js show/blacklist add <path>→node ${CLAUDE_PLUGIN_ROOT}/scripts/blacklist-manager.js add <path>/blacklist remove <path>→node ${CLAUDE_PLUGIN_ROOT}/scripts/blacklist-manager.js remove <path>/blacklist reset→node ${CLAUDE_PLUGIN_ROOT}/scripts/blacklist-manager.js reset
Format the JSON output as a readable summary:
- For
show: list the effective blacklist paths with a note about defaults vs user additions - For
add/remove/reset: confirm the action and show the updated list
The default blacklist automatically includes all ancestor directories from / to the user's home directory (e.g., /, /Users, /Users/<username>). This prevents accidentally indexing root or home directories. User additions are merged on top of these defaults. The whitelist overrides the blacklist for specific paths.
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.
- 3d ago First seen · 21 lines · 10 tokens per session scan A 2d45f74a5abd
blacklist is a command published in the GitHub repository sagarmk/beacon-plugin (43 stars, last pushed 13d ago), licensed MIT. It adds 10 tokens to every session and 273 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.