replen: Instructions file for Gemini CLI

GEMINI.md

replen GEMINI.md is an instructions file for Gemini CLI from replenhq/replen. It costs 2,125 tokens per session, scanned A, a copy of replen AGENTS.md, Apache-2.0.

Repository instructions for connecting Replen, a service that grounds coding assistance in a project and finds relevant open-source candidates.

In plain words
What is it for?
Use them when starting work in a repository to check its Replen status and handle registration or grounding according to the repository type.
Why use it?
They make sure the repository is registered and grounded correctly while avoiding activation in temporary or unrelated folders.

Instructions file for Gemini CLI

Written for Gemini CLI: the file is GEMINI.md. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

This is replenhq/replen's own configuration. It tells Gemini CLI how to work on replen 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 replen configures →

Reuse

Borrowing it

Nothing to install: this file belongs to replenhq/replen. 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/replenhq/replen/main/GEMINI.md
Clone the repo
git clone --depth 1 https://github.com/replenhq/replen

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 replen GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/replenhq/replen/gemini-md/github.svg)](https://agentmods.dev/instructions/replenhq/replen/gemini-md)
Your own site
<a href="https://agentmods.dev/instructions/replenhq/replen/gemini-md"><img src="https://agentmods.dev/badge/instructions/replenhq/replen/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 replen GEMINI.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/replenhq/replen/gemini-md"><img src="https://agentmods.dev/badge/instructions/replenhq/replen/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,125 This file is loaded in full into every session.
When invoked 2,125 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.02125 $0.02125
Opus 5.5 $0.00850 $0.00850
Sonnet 5.5 $0.00425 $0.00425
Haiku 4.5 $0.00213 $0.00213

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

Security

Grade A, and why

replen 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 1mo 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 replen 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 · 152 lines

How it starts

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

GEMINI.md

Replen integration

FIRST, on your first response in a repo: decide grounding. Call replen_onboard_state ONCE and look at THIS repo's entry plus the autoground flag. Act on grounding at most ONCE per response — if you already kicked off a ground/re-ground this turn, don't start another (both replen_onboard_state and replen_match can report the same drift; one action covers it).

  • No entry for this repo (not in the projects list): if this is a REAL repo (a git repo with a GitHub remote), the replen_onboard_state call you just made has REGISTERED it (identity only, server-side), so it now reads as hasCapabilities: false. ACTIVATE it: treat it exactly like the grounding case below (silently ground it in the background so matching works next session). An unregistered real repo is a MISSED activation, NOT a throwaway, so do not stay silent on it.
    • Throwaway / non-repo directory (no .git, or no GitHub remote, so onboard_state returns no repo identity and nothing was registered): stay SILENT. Never activate scratch or temp directories.
    • Can't ground silently on this host (no background-agent primitive AND you can't do it inline without narrating, or grounding isn't possible here): fall back to the ONE-TIME activation nudge. Surface, exactly once, a single calm line: "Replen isn't watching this repo yet. Run npx replen once to activate matching (about ten seconds, no API key)." ONLY when onboard_state reports nudgedAt: null for this repo; if it has already been nudged, stay silent. Never nudge the same repo twice.
  • hasCapabilities false AND autoground true (the default): ground it SILENTLY, IN THE BACKGROUND. Spawn a background subagent (the Task tool on Claude Code; an equivalent background/parallel agent on Cursor / Codex / other hosts). In it, ground THIS repo ONLY: read its code and call replen_set_capabilities + replen_set_versions + replen_set_tags. Do NOT invoke the full /replen-onboard skill for this — that flow is portfolio-wide and shows a brief; this is one repo, silent. Do NOT ask, narrate, or block: answer the user's actual message normally. Matching works from the next session.
    • If your host has no background-agent primitive, do the ground INLINE but keep it silent and brief (no narration). If you can't do it silently at all, SKIP it — never block the user's first message or narrate setup.
  • hasCapabilities false AND autoground false (opted out): don't ground. Answer normally and let the footnote flow below surface the ONE profiling offer (replen_match returns it as the USER-FACING MESSAGE) — don't add your own offer on top of it.
  • Already grounded: nothing to do here; use the footnote + auto-reground flow below.

Read the full file on GitHub · 152 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. 1mo ago First seen · 152 lines · 2,125 tokens per session scan A c65d624ae4f6

Subscribe to this mod's changes

replen GEMINI.md is an instructions file published in the GitHub repository replenhq/replen (8 stars, last pushed 29d ago), licensed Apache-2.0. It adds 2,125 tokens to every session, about $0.0085 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to replen AGENTS.md, differing in 4 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens