agentmods.dev

beacon-docs: Instructions file for Gemini CLI

GEMINI.md

beacon-docs GEMINI.md is an instructions file for Gemini CLI from Juliocbm/beacon-docs. It costs 1,182 tokens per session, scanned A, a copy of beacon-docs AGENTS.md, MIT.

Instructions for Gemini CLI that describe a project's documentation structure, naming rules, and when to create each kind of document.

In plain words
What is it for?
They guide Gemini CLI when creating plans, decision records, backlogs, evaluations, and other project documentation.
Why use it?
They give the coding agent a durable place for decisions and project work instead of relying on memory from a single chat.

Instructions file for Gemini CLI

Written for Gemini CLI: the file is GEMINI.md. Also seen: mentions Gemini CLI.

This is Juliocbm/beacon-docs's own configuration. It tells Gemini CLI how to work on beacon-docs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything beacon-docs configures →

not rated 6repo 5mo ago A scan 1,182 tokens copy · 95% MIT
View source ↗ Juliocbm/beacon-docs
Reuse

Borrowing it

Nothing to install: this file belongs to Juliocbm/beacon-docs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Juliocbm/beacon-docs/main/GEMINI.md
Clone the repo
git clone --depth 1 https://github.com/Juliocbm/beacon-docs

Made for: Gemini CLI.

Wrote 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.

agentmods badge for beacon-docs GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/juliocbm/beacon-docs/gemini-md/github.svg)](https://agentmods.dev/instructions/juliocbm/beacon-docs/gemini-md)
Your own site
<a href="https://agentmods.dev/instructions/juliocbm/beacon-docs/gemini-md"><img src="https://agentmods.dev/badge/instructions/juliocbm/beacon-docs/gemini-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for beacon-docs GEMINI.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/juliocbm/beacon-docs/gemini-md"><img src="https://agentmods.dev/badge/instructions/juliocbm/beacon-docs/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,182 This file is loaded in full into every session.
When invoked 1,182 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01182 $0.01182
Opus 5.5 $0.00473 $0.00473
Sonnet 5.5 $0.00236 $0.00236
Haiku 4.5 $0.00118 $0.00118

Measured 2mo ago against content hash ec67a4358f3a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

beacon-docs GEMINI.md 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 2mo 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.

Origin

This is a copy

95% identical to beacon-docs AGENTS.md — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

GEMINI.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GEMINI.md — Documentation Convention

Read by Gemini CLI. Full convention: docs/_meta/convention.md.

Universal rules

  1. One doc = one category. Never duplicate across folders.
  2. Status via folder, never filename. Closed plan → _archive/, never *_DONE.md or *_v2.md.
  3. kebab-case for all filenames. No camelCase, no snake_case, no spaces.
  4. README required in every category folder.
  5. ADRs are append-only. Supersede with a new ADR; never edit an accepted one.
  6. Evaluations are immutable snapshots. To revise, create a new dated file.
  7. Plans archive to _archive/ when done. Move them, never rename.
  8. Generated AI files (this one) must match docs/_meta/convention.md. Run beacon sync after editing the convention.
  9. Don't create folders outside the convention. Run beacon enable <addon> or propose an ADR.

Persistence rule: Decisions live in ADRs, multi-step work lives in plans, deferred work lives in backlog, retrospection lives in evals. Chat memory is session-scoped and lost when the conversation ends. If you find yourself relying on chat memory to track a decision, plan, or follow-up — write the document instead.

Project-specific rules

  • operations/*.guide.md — deploy guides, admin runbooks, troubleshooting. Post-mortems go in evaluations/.

Where does X go?

Question Folder
"How is X done technically?" reference/
"How is the system structured?" architecture/
"Why was X decided?" adr/
"What is being built right now?" plans/
"What is on the future backlog?" backlog/
"What was the state at date X?" evaluations/
"How do I deploy/administer X?" operations/

Workflow triggers — when to create documents

These are the conversational signals that should prompt you to create or update Beacon documents. Treat them as imperatives, not suggestions.

Read the full file on GitHub · 62 lines

Changes

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.

  1. 2mo ago First seen · 62 lines · 1,182 tokens per session scan A ec67a4358f3a

Subscribe to this mod's changes

beacon-docs GEMINI.md is an instructions file published in the GitHub repository Juliocbm/beacon-docs (6 stars, last pushed 5mo ago), licensed MIT. It adds 1,182 tokens to every session, about $0.0047 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to beacon-docs AGENTS.md, differing in 4 lines, and is treated as a copy.

Writing and docs
Related

beacon-docs GEMINI.md compared with instructions from other repositories

beacon-docs GEMINI.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
beacon-docs GEMINI.mdJuliocbm/beacon-docsInstructions file65mo agoMITA1,182Gemini CLI
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode