Borrowing it
Nothing to install: this file belongs to FreePeak/LeanKG. 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/FreePeak/LeanKG/main/AGENTS.mdgit clone --depth 1 https://github.com/FreePeak/LeanKGWrote 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/freepeak/leankg/agents-md)<a href="https://agentmods.dev/instructions/freepeak/leankg/agents-md"><img src="https://agentmods.dev/badge/instructions/freepeak/leankg/agents-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.
<a href="https://agentmods.dev/instructions/freepeak/leankg/agents-md"><img src="https://agentmods.dev/badge/instructions/freepeak/leankg/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.04395 | $0.04395 |
| Opus 5.5 | $0.01758 | $0.01758 |
| Sonnet 5.5 | $0.00879 | $0.00879 |
| Haiku 4.5 | $0.00439 | $0.00439 |
Grade A, and why
LeanKG AGENTS.md scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
— and `curl 127.0.0.1:9699` reached whichever held the IPv4 socket. So a How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LeanKG — Agent Context
Tech stack: Go 1.25 (module github.com/FreePeak/LeanKG) + SQLite (WAL, default) + PostgreSQL/pgvector (opt-in) + official MCP go-sdk. The Rust tree is removed; the repository root is the Go module.
Build & Test
make go-build # CGO_ENABLED=0 binaries into bin/ (leankg, leankg-embed)
make go-test # go test ./... -count=1 (54 packages)
go test ./internal/store/ -count=1 # one package
go test ./internal/store/ -run TestWatermark -v # one test; -run is an unanchored regex, so this matches TestWatermarkBumpsOnWrite (internal/store/store_test.go:215)
make go-vet # go vet ./...
make go-bench # benchmark/ab suite
make go-build-tstree # build with the tree-sitter tier (-tags tstree, CGO)
make go-test-tstree # test that same tier
make dual-engine # sqlite + live-PostgreSQL acceptance gate (needs :5433 pgvector)
make go-ui-assets # build ui-v2 and sync dist/ into internal/web/embed
Store contract: internal/store/backend.go (Backend interface; SQLite = *Store, PostgreSQL = PGStore). PG tests gate on LEANKG_TEST_PG_URL (local fixture: docker pgvector :5433, creds postgres/postgres, db leankg).
Test-layer policy (owner decision, 2026-09-14): unit tests stay in-process
and fast — no real provider/network calls, no sleeps; go test ./... is
the gate. Anything making a real embedding/LLM/PG call or measuring timing is
an integration/e2e test gated on an env var (LEANKG_TEST_PG_URL, live
sidecar) or its own job (ttfv); benchmarks (make go-bench,
benchmark/ab) never run in CI — they are explicit local/nightly tools.
The go-engine CI job runs only the in-process suite (both tag sets) with a
300 s budget.
Testing conventions
- Unit tests live in
_test.gofiles beside the package they cover. - Fixtures live under
testdata/(for exampleinternal/index/testdata/). - Use
t.TempDir()for tests that need filesystem access. - Tree-sitter tests need the
tstreebuild tag (internal/tstree/tstree_test.go:1):go test -tags tstree ./internal/tstree/ -count=1.
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.
- 8d ago Changed · +12 lines · +364 tokens per session c9b006c7605c
- 9d ago Changed · +6 lines · +334 tokens per session 120e1f126bcc
- 12d ago Changed · +34 lines · +613 tokens per session 4c075a01d94c
- 15d ago Changed · +2 lines · +515 tokens per session db5fa86c731d
- 17d ago Changed · +35 lines · +477 tokens per session 11e700929297
- 19d ago Changed · +6 lines · +248 tokens per session 85cef5637371
- 1mo ago Changed · -8 lines · -27 tokens per session 7bfe1dfd33b6
- 1mo ago Changed · -4 lines · -26 tokens per session f14f93ba6d27
- 1mo ago Changed · +55 tokens per session 15f71326cbd9
- 1mo ago First seen · 120 lines · 1,842 tokens per session scan A b13d70cb2084
LeanKG AGENTS.md is an instructions file published in the GitHub repository FreePeak/LeanKG (222 stars, last pushed 8d ago), licensed Apache-2.0. It adds 4,395 tokens to every session, about $0.0176 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
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.
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).
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 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).
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.