Borrowing it
Nothing to install: this file belongs to hollandkevint/thinkhaven. 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/hollandkevint/thinkhaven/main/GEMINI.mdgit clone --depth 1 https://github.com/hollandkevint/thinkhavenWrote 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/hollandkevint/thinkhaven/gemini-md)<a href="https://agentmods.dev/instructions/hollandkevint/thinkhaven/gemini-md"><img src="https://agentmods.dev/badge/instructions/hollandkevint/thinkhaven/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.00942 | $0.00942 |
| Opus 5 | $0.00471 | $0.00471 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
thinkhaven 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compound Project - Agent Configuration
Project Overview
This project implements the Compound Learning System for thinkhaven - a self-improving knowledge system based on the "Compounding Engineering" philosophy.
Core Principle
Each unit of engineering work should make subsequent units of work easier—not harder.
Workflows Available
Full index: See .agent/workflows/README.md for all commands and quick start guide.
Use these commands for systematic development:
| Command | When |
|---|---|
/explore |
Deep investigation before planning |
/specs |
Before multi-week initiatives |
/plan |
Before starting significant work |
/work |
Execute plans systematically |
/review |
Before merging, self-review |
/compound |
After solving problems ("that worked!") |
/housekeeping |
Before git push (cleanup & archive) |
Knowledge Persistence
Solutions are documented in docs/solutions/ and explorations in docs/explorations/ with:
- YAML frontmatter for searchability
- Categorized by problem type
- Schema validated (
schema.yaml)
Before solving a problem: Search docs/solutions/ and docs/explorations/ for prior knowledge.
After solving a problem: Run /compound to document it.
Compounding Loop
/explore (optional) → /specs (large) → /plan (per phase) → /work → /review → /compound → /housekeeping → repeat
Important Directories
.agent/workflows/ # All workflow commands
docs/solutions/ # Persistent knowledge base
docs/explorations/ # Deep investigations & research
docs/decisions/ # Project-wide ADRs
├── patterns/ # Critical patterns (READ FIRST)
├── schema.yaml # Validation schema
└── {categories}/ # Categorized solutions
docs/features/ # Feature documentation (New features, READMEs)
skills/ # Modular capabilities
├── file-todos/ # Todo management
├── compound-docs/ # Solution documentation
└── session-resume/ # Context resume
plans/ # Implementation plans from /plan
├── archive/ # Completed plans
todos/ # Work items from /review
├── archive/ # Completed todos
docs/specs/ # Multi-session specifications
├── archive/ # Completed specs
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.
- 4d ago First seen · 84 lines · 942 tokens per session scan A d7cb82f801a8
thinkhaven GEMINI.md is an instructions file published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 942 tokens to every session, about $0.0047 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-09-03.
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.