What is mindgap AGENTS.md?

A set of project instructions for adding knowledge to the Mindgap graph, including rules for checking existing information and linking new entries.

Use it when an agent researches topics or writes nodes and links into a Mindgap knowledge graph.

It reduces duplicate or incomplete knowledge and keeps added information traceable to its sources.

mindgap AGENTS.md — Instructions file by grburgess

Install

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.

agentmods

npx agentmods add instructions/grburgess/mindgap/agents-md

Clone the repo

git clone --depth 1 https://github.com/grburgess/mindgap

Made for: Codex, OpenCode.

Per session 1,212 This file is loaded in full into every session.

When invoked 1,212 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.01212	$0.01212
Opus 5	$0.00606	$0.00606
Sonnet 5	$0.00242	$0.00242
Haiku 4.5	$0.00121	$0.00121

Measured yesterday against content hash fd64cd81b49c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mindgap 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 yesterday.

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.

AGENTS.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — knowledge protocol for loop sessions

You are a loop session adding knowledge to the mindgap graph. CLI: mindgap (on PATH) or python3 -m mindgap from this repo. DB: default ~/.mindgap/mindgap.db (env MINDGAP_DB/MINDGAP_HOME override).

Two interfaces, same db: the CLI (above) and the MCP server (python3 -m mindgap.mcp, registered in .mcp.json — tools mindgap_ingest/mindgap_find/mindgap_context/mindgap_link/etc.). Prefer the MCP tools when available: mindgap_ingest enforces the rules below (rejects dangling-endpoint payloads whole, requires created_by, returns the persisted rows) so you can't silently desync. The rules in this file apply identically whichever interface you use.

MUST rules

Run mindgap context "<topic>" BEFORE researching a topic — read what exists, avoid duplicates, build on existing nodes.
Write via mindgap ingest - with created_by = your loop name (e.g. loop:confluence-scan) on every node and edge.
Every node sourced from Confluence/GitHub/arXiv MUST carry a urls entry ({"label","url","kind"}; kind: confluence|github|arxiv|web).
Use [[wiki-links]] in bodies to densify the graph — each [[node-id]] auto-creates a mentions edge (stub node if target missing). Wiki-links MUST use the exact node id (check with mindgap find), not the title or a guessed slug — [[maestro]] is a dangling stub if the node is repo-maestro.
Prefer upserting existing ids over creating near-duplicate new nodes — run mindgap find first (see below).
Run mindgap export at session end (snapshot to ~/.mindgap/snapshots/).

Vocabularies

Node type: concept | definition | software | repo | page | paper | person | team | stub
Edge rel: relates_to | defines | implements | depends_on | cites | part_of | mentions

Near-duplicate check

Before creating a node, search by likely slug fragments and title words:

mindgap find "vector db" --json
mindgap find "vector-database" --type concept

Read the full file on GitHub · 98 lines

Changes

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.

yesterday First seen · 98 lines · 1,212 tokens per session scan A fd64cd81b49c

Subscribe to this mod's changes

mindgap AGENTS.md is an instructions file published in the GitHub repository grburgess/mindgap (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,212 tokens to every session, about $0.0061 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.

Research

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

mindgap AGENTS.md