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/chris-peterson/beacon/install-beacongit clone --depth 1 https://github.com/chris-peterson/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/chris-peterson/beacon/install-beacon)<a href="https://agentmods.dev/commands/chris-peterson/beacon/install-beacon"><img src="https://agentmods.dev/badge/commands/chris-peterson/beacon/install-beacon.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.00018 | $0.00225 |
| Opus 5 | $0.00009 | $0.00112 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
install-beacon 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 beacon's install bootstrap, then report its output as-is — one line if every step was already current. Do no other work.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/beacon" install ${ARGUMENTS}
Every step is idempotent, so re-running it is the normal way to recover from drift — the SessionStart freshness hook nudges you here when beacon --version falls behind the plugin.
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 · 20 lines · 18 tokens per session scan A d51d1d561ada
install-beacon is a command published in the GitHub repository chris-peterson/beacon (1 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 225 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-31.
Other commands, from other repositories
browse
Generate a single-file markdown browser HTML — tree sidebar + marked.js render. Scans project docs/ + /.claude/{plans,projects} by default.
lint
Validate frontmatter + body conventions across all project docs (without rebuilding the dashboard).
render
Run docs-cockpit render — regenerates docs/index.html + docs/state.json from the project's docs-cockpit.yaml.
migrate
One-shot migrate an existing project's scattered MDs (docs/plans/, docs/adrs/, etc.) into docs-cockpit's canonical docs/spec/module/ layout, with auto-generated frontmatter and yaml.
update
Update docs-cockpit (CLI + plugin) · delegates to docs-cockpit upgrade CLI for atomic one-command upgrade.
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.