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 skills/juliocbm/beacon-docs/beacon-initnpx skills add Juliocbm/beacon-docs --skill beacon-initgit clone --depth 1 https://github.com/Juliocbm/beacon-docsWrote 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/skills/juliocbm/beacon-docs/beacon-init)<a href="https://agentmods.dev/skills/juliocbm/beacon-docs/beacon-init"><img src="https://agentmods.dev/badge/skills/juliocbm/beacon-docs/beacon-init.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.00035 | $0.03247 |
| Opus 5 | $0.00017 | $0.01623 |
| Sonnet 5 | $0.00007 | $0.00649 |
| Haiku 4.5 | $0.00003 | $0.00325 |
Grade A, and why
beacon-init 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 4d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/beacon:beacon-init
Initializes beacon-docs in the current project. beacon init is destructive in surprising ways — it creates persistent artifacts (folders, config, generated AI rule files at the project root) that are annoying to undo. This skill exists to make sure init only happens (a) on appropriate state, (b) with the right type+add-ons inference, (c) with user consent over the choices that are team intent rather than mechanical.
Core principle
Asymmetric blast radius justifies asymmetric caution. A wasted turn confirming state costs the user 30 seconds. A misapplied init overwrites their CLAUDE.md, scaffolds folders that compete with existing docs, and forces a git revert. Read state first, then act.
First action: state detection
Before anything else, run these checks in parallel (single message, multiple tool calls):
# 1. Is beacon-docs already initialized here?
test -f docs/_meta/beacon.config.json && cat docs/_meta/beacon.config.json
# 2. What's in docs/ if it exists?
ls -la docs/ 2>/dev/null
# 3. What kind of project is this?
test -f package.json && cat package.json
ls -la # top-level structure
These four reads give you everything needed to pick the right mode.
The 5 modes
Based on what state-detection finds, pick exactly one of these:
Mode 1 — Already initialized (config exists)
docs/_meta/beacon.config.json is present. Refuse to re-init.
This project is already initialized with beacon-docs:
- Project type: <projectType from config>
- Enabled categories: <categories>
- AI agents: <agents>
Re-running `beacon init` would overwrite CLAUDE.md, .cursorrules, and possibly
hand-edited READMEs. You probably want one of:
- `beacon enable <addon>` — to add categories (compliance, business, ...)
- `beacon disable <addon>` — to remove categories
- `beacon sync` — to regenerate AI files from convention.md
- `beacon about` — to see current state in one place
If you really want a destructive reset, confirm "yes, wipe and restart" and
I'll run `beacon init --yes --type=... --force` — but only with your explicit
acknowledgment that current customizations to CLAUDE.md / .cursorrules will
be lost.
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.
- 4d ago First seen · 262 lines · 35 tokens per session scan A 9d194c2227f6
beacon-init is a skill published in the GitHub repository Juliocbm/beacon-docs (6 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 3,247 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…