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 instructions/replenhq/replen/gemini-mdgit clone --depth 1 https://github.com/replenhq/replenWhat 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.02125 | $0.02125 |
| Opus 5 | $0.01063 | $0.01063 |
| Sonnet 5 | $0.00425 | $0.00425 |
| Haiku 4.5 | $0.00213 | $0.00213 |
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 2d 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.
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.
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
projectslist): if this is a REAL repo (a git repo with a GitHub remote), thereplen_onboard_statecall you just made has REGISTERED it (identity only, server-side), so it now reads ashasCapabilities: 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, soonboard_statereturns 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 replenonce to activate matching (about ten seconds, no API key)." ONLY whenonboard_statereportsnudgedAt: nullfor this repo; if it has already been nudged, stay silent. Never nudge the same repo twice.
- Throwaway / non-repo directory (no
hasCapabilitiesfalse ANDautogroundtrue (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 callreplen_set_capabilities+replen_set_versions+replen_set_tags. Do NOT invoke the full/replen-onboardskill 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.
hasCapabilitiesfalse ANDautogroundfalse (opted out): don't ground. Answer normally and let the footnote flow below surface the ONE profiling offer (replen_matchreturns 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.
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.
- 2d ago First seen · 152 lines · 2,125 tokens per session scan A c65d624ae4f6
replen GEMINI.md is an instructions file published in the GitHub repository replenhq/replen (8 stars, last pushed 22d ago), licensed Apache-2.0. It adds 2,125 tokens to every session, about $0.0106 per session on Opus 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.
Other instructions, from other repositories
codevira CLAUDE.md
Instructions for sachinshelke/codevira, covering codevira — persistent project memory, when to call which codevira tool, at the start of every session, before modifying any file and before adopting a pattern, library, or naming convention.
codevira AGENTS.md
Instructions for sachinshelke/codevira, covering codevira-tracked project memory: codevira, locked decisions (donotrevert), active conventions, codevira — persistent project memory and when to call which codevira tool.
codevira GEMINI.md
Instructions for sachinshelke/codevira, covering codevira — persistent project memory, when to call which codevira tool, at the start of every session, before modifying any file and before adopting a pattern, library, or naming convention.
ai-mind-map copilot-instructions.md
Copilot instructions for shdra06/ai-mind-map, covering ai mind map mcp — code memory engine (v1.4.0), 🚀 first thing to do in every conversation, quick lookup: "i need to..." → use this tool, ⚡ session lifecycle (always use these) and 🔍 find code (instead of grep/reading files).
ai-mind-map CLAUDE.md
Claude Code instructions for shdra06/ai-mind-map, covering ai mind map mcp — code memory engine (v1.4.0), 🚀 first thing to do in every conversation, quick lookup: "i need to..." → use this tool, ⚡ session lifecycle (always use these) and 🔍 find code (instead of grep/reading files).
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).