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.
npx agentmods add instructions/maxkle1nz/m1nd/agents-mdgit clone --depth 1 https://github.com/maxkle1nz/m1ndWrote 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/maxkle1nz/m1nd/agents-md)<a href="https://agentmods.dev/instructions/maxkle1nz/m1nd/agents-md"><img src="https://agentmods.dev/badge/instructions/maxkle1nz/m1nd/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 | $0.10042 | $0.10042 |
| Opus 5 | $0.05021 | $0.05021 |
| Sonnet 5 | $0.02008 | $0.02008 |
| Haiku 4.5 | $0.01004 | $0.01004 |
Grade A, and why
m1nd 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 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 — 546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working guide for any coding agent on m1nd
Vendor-neutral instructions for autonomous agents (Jules, Codex, Claude Code, Cursor, …) working on this repository. Read this first; it is the contract.
m1nd is a neuro-symbolic code-graph engine in Rust (workspace, resolver 2, six
members): m1nd-core (in-memory engine) · m1nd-ingest (extractors / write side) ·
m1nd-mcp (the served MCP owner + every verb) · m1nd-control · m1nd-runnerd (the
write/execution lane — the only spawner) · m1nd-openclaw. Outside the Rust workspace:
m1nd-ui (the served web UI, Vite/React), m1nd-demo, and an npm wrapper in npm/. Philosophy: agent-first, proof-grown,
local-first, calibrated honesty (absent/abstain/insufficient_evidence are real answers).
This is a PUBLIC repository. Everything you commit is published.
The gates (must pass — these ARE the CI)
Run these before you consider any change done. The blocking gate is ubuntu + macOS:
cargo nextest run --workspace --all-targets # the LOCAL canonical runner (one process per test)
cargo test --workspace --doc # the sentinels nextest never runs
cargo clippy --workspace --all-targets -- -D warnings # warnings fail the build
cargo fmt --check
nextest is the canonical runner ON YOUR MACHINE (adopted 2026-08-02, measured:
same suite 641–935s under cargo test, 377s under nextest, 1643/1643 —
including the two deadlock-timeout tests that expire under cargo test's
shared-process load). Retries are 0 by policy — a flake goes red. Plain
cargo test still works when you need --nocapture on one test.
CI's required legs still run cargo test, deliberately: the same measurement
taken ON THE GATE said no — ubuntu went 62→83 min under nextest (the
nested-Cargo process storm on the weakest-I/O runner) while windows improved
70→48. A nextest-shadow job collects gate-side timing on main pushes; the
required legs switch only when the shadow reproduces the gate's greens and
reds at an acceptable wall. Local green under nextest + gate green under
cargo test are BOTH required truths until then — do not "fix" one by
trusting the other.
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 · 546 lines · 10,042 tokens per session scan A a9a55c464213
m1nd AGENTS.md is an instructions file published in the GitHub repository maxkle1nz/m1nd (22 stars, last pushed today), licensed MIT. It adds 10,042 tokens to every session, about $0.0502 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-30.
Other instructions, from other repositories
roam-code AGENTS.md
AGENTS.md instructions for Cranot/roam-code, covering agents.md — roam-code development guide, what this project is, documentation hub, where files go (private vs public) and quality discipline (from internal/dogfood/ + agi-in-md).
trace-mcp CLAUDE.md
Claude Code instructions for nikolai-vysotskyi/trace-mcp, covering trace-mcp development guide, what this project is, agent behavior — read before every task, no flattery, no filler and disagree when the premise is wrong.
trace-mcp AGENTS.md
AGENTS.md instructions for nikolai-vysotskyi/trace-mcp: IMPORTANT: For ANY code exploration task, ALWAYS use trace tools first. NEVER use Read/Grep/Glob/Bash(ls,find) for navigating source code.
CodeStory AGENTS.md
AGENTS.md instructions for TheGreenCedar/CodeStory, covering codestory agent guide, start here, ownership boundaries, product invariants and identity and configuration.
reposkein AGENTS.md
AGENTS.md instructions for reposkein/reposkein, covering reposkein knowledge base, hard invariants (ci-enforced — never break), structure, where to look and conventions (this repo only).
CodeStory copilot-instructions.md
Copilot instructions for TheGreenCedar/CodeStory: Use CodeStory proactively for repository questions. Do not wait for the user to mention it by name.