Borrowing it
Nothing to install: this file belongs to epicsagas/Episteme. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/epicsagas/Episteme/main/GEMINI.mdgit clone --depth 1 https://github.com/epicsagas/EpistemeWrote 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/instructions/epicsagas/episteme/gemini-md)<a href="https://agentmods.dev/instructions/epicsagas/episteme/gemini-md"><img src="https://agentmods.dev/badge/instructions/epicsagas/episteme/gemini-md.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.1 | $0.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
Episteme 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 7d 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.
What it actually says
epic-harness
This project uses epic-harness for AI quality automation.
Commands
- /spec — define requirements
- /go — build with TDD (sequential execution)
- /check — sequential review + audit + tests
- /ship — PR creation + CI
- /evolve — skill evolution status
- /team — design or update an org-level agent team
Auto-behaviors
- Before coding: read
~/.harness/projects/{slug}/memory/for project context - After each task: verify build+tests pass
- On security-related code: run secure skill checklist
- On large files (>200 lines): run simplify skill
Hook Events
- BeforeAgent →
epic-harness resume(restore session + load skills) - AfterAgent →
epic-harness reflect(evolve skills + save metrics) - AfterModel →
epic-harness observe(record tool scores, async) - BeforeModel →
epic-harness guard(scan for dangerous shell patterns)
Notes
- Gemini CLI does not support parallel agent spawning — all tasks run sequentially
- Guard runs at BeforeModel level (no PreToolUse equivalent in Gemini CLI)
- Evolved skills stored in
~/.harness/projects/{slug}/evolved/, backed up in~/.harness/projects/{slug}/evolved_backup/
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.
- 7d ago First seen · 29 lines · 299 tokens per session scan A 3521a0ecf6cc
Episteme GEMINI.md is an instructions file published in the GitHub repository epicsagas/Episteme (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 299 tokens to every session, about $0.0015 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.