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-archivenpx skills add Juliocbm/beacon-docs --skill beacon-archivegit 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-archive)<a href="https://agentmods.dev/skills/juliocbm/beacon-docs/beacon-archive"><img src="https://agentmods.dev/badge/skills/juliocbm/beacon-docs/beacon-archive.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.00071 | $0.03075 |
| Opus 5 | $0.00036 | $0.01537 |
| Sonnet 5 | $0.00014 | $0.00615 |
| Haiku 4.5 | $0.00007 | $0.00308 |
Grade A, and why
beacon-archive 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/beacon:beacon-archive
Moves shipped plans (and roadmaps) to _archive/ after surfacing context for informed consent. This skill performs DESTRUCTIVE filesystem operations — every action requires the user's explicit confirmation, and --force is always a separate consent.
Core principle
Read context. Propose informed. Confirm. Execute.
The CLI's beacon archive command moves files between directories. The operation is recoverable via git but annoying to undo, and silently archiving the wrong plan loses days of in-flight context. Every code path in this skill must end with the user's explicit yes before any move happens.
First action: state detection in parallel
Read the inputs needed for any subsequent decision:
# 1. What types are archivable in this project?
cat docs/_meta/beacon.config.json | jq '.categories' # check roadmaps add-on
# 2. What active plans exist?
ls docs/plans/*.plan.md 2>/dev/null
# 3. What active roadmaps exist (if add-on enabled)?
ls docs/roadmaps/*.roadmap.md 2>/dev/null
Run these in parallel (single message, multiple tool calls). Then branch based on what you find.
Detect invocation mode
| User input | Mode |
|---|---|
/beacon:beacon-archive (no arg) |
Selection mode — list items, let user pick |
/beacon:beacon-archive <slug> |
Direct mode — propose specific item, confirm once |
Selection mode (most common)
Step 1 — Enumerate AND read
Glob for plans and roadmaps in parallel. Then Read each file in parallel to get checkbox state. Reading is non-optional — checkbox state is the primary "is this done?" signal; mtime is tiebreaker.
Step 2 — Empty state
If no active plans (or roadmaps) exist:
No active plans to archive.
Period. One line. Stop.
Do NOT dump _archive/ contents, do NOT suggest "create a plan first", do NOT apologize. Empty is an answer, not an absence of one. The "earn the turn by padding" pull is the same calibration bug from beacon-doctor's all-clear case — resist it.
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 · 239 lines · 71 tokens per session scan A 84ded5c4a5c7
beacon-archive is a skill published in the GitHub repository Juliocbm/beacon-docs (6 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 3,075 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…