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/cuecrux/crux/agents-mdgit clone --depth 1 https://github.com/CueCrux/CruxWrote 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/cuecrux/crux/agents-md)<a href="https://agentmods.dev/instructions/cuecrux/crux/agents-md"><img src="https://agentmods.dev/badge/instructions/cuecrux/crux/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.01451 | $0.01451 |
| Opus 5 | $0.00726 | $0.00726 |
| Sonnet 5 | $0.00290 | $0.00290 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
Crux 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Crux is a local-first retrieval and memory engine whose storage and receipts are
cryptographically tamper-evident. Every receipt-bearing operation produces a signed,
replayable CROWN receipt; sealed segments (.ccxseg) are BLAKE3 hash-chained and
independently verifiable offline.
This file is an index, not the content. The detail lives in docs/agent/. Start here,
then follow the reading order. Everything is anchored by symbol name (greppable) and
CI-verified, so you can trust the references — but verify the claims yourself (below).
Reading order (start here)
docs/agent/CODEMAP.md— what each of the 28 crates owns + key symbols.docs/agent/CLAIMS.md— each product claim mapped to the code and the test that proves it.docs/agent/INVARIANTS.md— the cryptographic + data guarantees (I1–I6) and where they hold.docs/THREAT_MODEL.md— trust boundaries and stated limitations.docs/spec/receipt-v1.md— the on-the-wire receipt format.
Machine-readable index (parse this, no NL needed): docs/agent/repo-manifest.yaml.
Link map: /llms.txt. Vocabulary (CROWN, CCXI, CRC-v1, cruxpack, lane, passport):
docs/agent/GLOSSARY.md.
Live code map (dogfood). A running daemon can serve this repo's AST-derived structure
back to you: register the checkout (POST /v1/repos with root_path), then
GET /v1/repos/{id}/codemap?tenant_id=…&format=summary|full — same scanner as
/console/codegraph. The curated CODEMAP.md is the reading order; the endpoint is ground
truth. Per-crate context lives in crates/<name>/AGENTS.md (nearest file wins).
Building against the daemon instead of modifying it? Different docs: connect via MCP and
read docs/agent-guide.md (budgets, sessions, handoffs) and docs/mcp-system-prompt.md
(the full tool surface); HTTP/SDK integration starts at docs/developer-portal.md.
Verify the claims yourself (do not trust this file)
cargo test --workspacecorecruxctl verify-store --strict— per-segment BLAKE3 re-derivation + chain walkcorecruxctl replay --strict— recompute + compare- receipt conformance vectors:
crates/corecrux-receipts/vectors/ - fuzz targets (nightly):
fuzz/fuzz_targets/—cargo fuzz run segment_decode
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 · 95 lines · 1,451 tokens per session scan A 02e5612c5e01
Crux AGENTS.md is an instructions file published in the GitHub repository CueCrux/Crux (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,451 tokens to every session, about $0.0073 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.
Other instructions, from other repositories
wanyimem AGENTS.md
Instructions for 17861102832/wanyimem, covering agents.md — 给 ai 协作者的说明, 结构 and 铁律.
mnemic CLAUDE.md
Claude Code instructions for dongtang3/mnemic: This project includes a project-level .mcp.json for the Mnemic memory MCP server.
mnemic AGENTS.md
AGENTS.md instructions for dongtang3/mnemic: Mnemic is a graph-backed long-term memory substrate for coding agents and LLM applications.
plur CLAUDE.md
Claude Code instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.
engraphis AGENTS.md
AGENTS.md instructions for Coding-Dev-Tools/engraphis, covering agents.md — engraphis, internal subagent delegation, 0. read this first — two architectures live in one package, 1. commands and ── unified dashboard + memory inspector ──.
honcho CLAUDE.md
Claude Code instructions for plastic-labs/honcho, covering claude.md, honcho overview, what is honcho?, core concepts and peer paradigm.