Borrowing it
Nothing to install: this file belongs to Kromatic-Innovation/athenaeum. 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/Kromatic-Innovation/athenaeum/develop/AGENTS.mdgit clone --depth 1 https://github.com/Kromatic-Innovation/athenaeumWrote 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/kromatic-innovation/athenaeum/agents-md)<a href="https://agentmods.dev/instructions/kromatic-innovation/athenaeum/agents-md"><img src="https://agentmods.dev/badge/instructions/kromatic-innovation/athenaeum/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/kromatic-innovation/athenaeum/agents-md"><img src="https://agentmods.dev/badge/instructions/kromatic-innovation/athenaeum/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.01823 | $0.01823 |
| Opus 5 | $0.00911 | $0.00911 |
| Sonnet 5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00182 | $0.00182 |
Grade A, and why
athenaeum 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 2d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Athenaeum — Agent Policy
GitHub
- Owner: Kromatic-Innovation
- Repo: athenaeum
- Package: athenaeum on PyPI
- License: Apache 2.0
Project overview
Athenaeum is an entity-centric long-term memory system for AI agents. Published to PyPI; tagged releases ship to real users.
Deployment boundary — this repo ships mechanism, not policy
Athenaeum is the engine. A running deployment — its configuration, its corpus, and the state of that corpus — lives outside this repository, at a location the operator configures. Nothing tracked here should name, assume, or depend on any particular deployment.
Two consequences for anything you write in this repo:
- No operator specifics in tracked files. No real names, addresses, or identifiers drawn from a live corpus; no absolute or home-relative paths to one. Documentation examples use invented people and organizations.
- Corpus-state work is not tracked here. An issue of the form "repair these N pages", "relocate these records", "provision this credential", or "arm this ceiling on the live deployment" describes one operator's data, not a defect in the engine. It belongs in that deployment's own tracker.
The dividing line is what the work is about, not who can run it. An
issue only the operator can execute — because it needs a host, a credential, or
a human decision — still belongs here when what it produces is evidence about
the engine: a parity report, a benchmark, a comparison that informs the design.
Label those ~operator and leave them in place.
When those two pull in different directions, ask what closes the issue. If closing it means writing a finding into the project's record — a number, a verdict, a recommendation that changes what the engine should do — it belongs here, however much deployment state it had to touch along the way. If closing it means leaving a deployment in a different state, it does not. An issue that would be closed by both is two issues: keep the finding here, and file the state change against the deployment.
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.
- 2d ago Changed · +36 lines · +466 tokens per session c48209a226fd
- 9d ago First seen · 120 lines · 1,357 tokens per session scan A e2655dd66f32
athenaeum AGENTS.md is an instructions file published in the GitHub repository Kromatic-Innovation/athenaeum (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,823 tokens to every session, about $0.0091 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
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.
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.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
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.