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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/hollandkevint/thinkhaven/agents-md"><img src="https://agentmods.dev/badge/instructions/hollandkevint/thinkhaven/agents-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.02028 | $0.02028 |
| Opus 5 | $0.01014 | $0.01014 |
| Sonnet 5 | $0.00406 | $0.00406 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
thinkhaven AGENTS.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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Last Updated: 2026-03-26
Project Context
ThinkHaven - Decision accelerator for structured AI sessions
- Tech Stack: Next.js 15.5, React 19, TypeScript, Supabase, Stripe, Anthropic Codex
- Architecture: Monorepo with Next.js app in
apps/web/ - Deployment: Vercel project
thinkhaven(https://thinkhaven.co) - Documented Solutions:
docs/solutions/contains searchable solution notes for past bugs, architecture patterns, conventions, and workflow issues, organized by category with YAML frontmatter (module,problem_type,tags). Relevant when implementing or debugging in documented areas.
Essential Commands
All commands run from apps/web/:
npm run dev # Dev server (localhost:3000, Turbopack)
npm run build # Production build
npm run lint # ESLint
npm test # Unit tests (Vitest, watch mode)
npm run test:run # Unit tests (once)
npm run test:e2e # E2E tests (Playwright, 7 smoke tests)
npm run test:prod # Smoke tests against production (15 tests)
Migrations: apps/web/supabase/migrations/ (001 → 017, sequential, never skip)
Route Architecture
Protected (/app/* - requires auth):
/app- Dashboard/app/new- New session/app/session/[id]- Active session workspace/app/account- Account settings
Public: / (landing), /try (guest, 10 msg limit), /demo, /assessment
Legacy redirects: /dashboard → /app, /bmad → /app/new, /workspace/[id] → /app/session/[id], /account → /app/account
Environment Variables
See .env.example. Required: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, ANTHROPIC_API_KEY, STRIPE_SECRET_KEY, NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY, STRIPE_WEBHOOK_SECRET, NEXT_PUBLIC_APP_URL. Optional: OPENROUTER_API_KEY (server-only fallback for guest synthesis when Anthropic is unavailable; OPENROUTER_MODEL and AI_PROVIDER=openrouter tune it — streaming/tool chat paths are not covered).
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.
- 3d ago First seen · 93 lines · 2,028 tokens per session scan A 129364107164
thinkhaven AGENTS.md is an instructions file published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 2,028 tokens to every session, about $0.0101 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.