neotoma AGENTS.md

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/markmhendrickson/neotoma/agents-md

Clone the repo

git clone --depth 1 https://github.com/markmhendrickson/neotoma

Made for: Codex, OpenCode.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/markmhendrickson/neotoma/agents-md.svg)](https://agentmods.dev/instructions/markmhendrickson/neotoma/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/markmhendrickson/neotoma/agents-md"><img src="https://agentmods.dev/badge/instructions/markmhendrickson/neotoma/agents-md.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

Origin unknown 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.01462	$0.01462
Opus 5	$0.00731	$0.00731
Sonnet 5	$0.00292	$0.00292
Haiku 4.5	$0.00146	$0.00146

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

Security

Grade A, and why

neotoma 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 today.

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 · 96 lines

How it starts

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

Neotoma Project Instructions for Codex

Document Loading Order (MANDATORY)

Every session MUST begin by loading these documents in this order:

docs/context/index_rules.mdc — Primary entrypoint; complete documentation map, reading strategies, dependency graph
Foundation documents from docs/foundation/ in this order:
- core_identity.md — What Neotoma is and is not (State Layer scope)
- philosophy.md — Core principles and architectural invariants
- layered_architecture.md — State Layer (Neotoma) and Operational Layer(s) above it
- product_principles.md — Product design principles
- agent_instructions_rules.mdc — Repository-wide agent instructions and validation checklist
Task-specific docs as indicated by the index (e.g. subsystems, architecture, testing)
- For install / MCP / configuration tasks: MUST load install.md (repo root) before any work involving installing Neotoma, configuring MCP entries, setting up LaunchAgents, changing data directories, or onboarding a new environment. install.md is the canonical CLI-driven setup sequence; never substitute shell introspection or hand-editing of config files for the CLI commands documented there.

Why this order: Foundation establishes constraints (determinism, immutability, State Layer boundaries) that all work must respect.

Core Constraints (Summary)

Full constraints in docs/foundation/agent_instructions_rules.mdc and .Codex/rules/. Summary:

MUST enforce:

State Layer boundaries: No strategy, execution, or inference logic in Neotoma; operational concerns live in the operational layer(s) above
Determinism: No random IDs, no unstable sorting, hash-based entity/event IDs
Immutability: Observations and source are immutable (reinterpretation creates NEW observations)
Schema-first: Use application types from docs/subsystems/record_types.md
Explicit control: User approves all ingestion; no background scanning
Provenance: All outputs trace to source + config + timestamp
Graph integrity: No orphans, no cycles, transactional writes
Privacy: No PII in logs (IDs only)

Read the full file on GitHub · 96 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.

today First seen · 96 lines · 1,462 tokens per session scan A 9844f92f1913

Subscribe to this mod's changes

neotoma AGENTS.md is an instructions file published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed yesterday), licensed MIT. It adds 1,462 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-09-03.

Documents agent-infrastructure agent-memory ai-agents deterministic-state entity-resolution event-sourcing

instar CLAUDE.md

Claude Code instructions for JKHeadley/instar, covering claude.md — instar, what this project is, quick reference, architecture and development workflow.

JKHeadley/instar · 5,924 tokens

Core-Memory CLAUDE.md

Instructions for JohnnyFiv3r/Core-Memory, covering claude.md — core memory, what this repo is, guiding principle — engineering simplicity, boring primitives, rich views and mapping to the current codebase.

JohnnyFiv3r/Core-Memory · 2,772 tokens

open-bridge CLAUDE.md

Instructions for bks-lab/open-bridge, a project described as: Your AI coding agent starts every session knowing your repos, your clients, and how you work — a plain git repo of markdown + YAML it reads at session start, independent of model or frontend. Context compounds instead of restarting. MIT.

bks-lab/open-bridge · 551 tokens