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/knaisoma/data-olympus/agents-mdgit clone --depth 1 https://github.com/knaisoma/data-olympusWrote 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/knaisoma/data-olympus/agents-md)<a href="https://agentmods.dev/instructions/knaisoma/data-olympus/agents-md"><img src="https://agentmods.dev/badge/instructions/knaisoma/data-olympus/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.01583 | $0.01583 |
| Opus 5 | $0.00792 | $0.00792 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
data-olympus 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Olympus
Project Overview
Data Olympus is the knowledge base service that coding agents consult before making decisions. It indexes the company-knowledge corpus and serves it over MCP and REST, and it enforces that agents consult it before governed changes.
It is the authority behind the tier model (T1 Universal, T2 Stack, T3 Project, T4 Component; see GDEC-017), decisions, and workflows.
Stack, as declared in pyproject.toml:
- Python
>=3.13, managed withuv - Runtime dependencies are deliberately few:
fastmcp,pydantic,pyyaml,regex - Two entry points:
data-olympus-mcp(the MCP server) anddata-olympus(the CLI)
There is no web framework and no database server. Keep it that way unless a decision says otherwise: the small dependency surface is a feature, because this service is a dependency of every other project's agent workflow.
Architecture
Storage is SQLite. The index lives at KB_INDEX_PATH (default /index/kb.db) and is rebuilt atomically into a temporary file before being swapped in.
Retrieval is a SQLite FTS5 index with BM25 ranking, layered with progressively broader fallbacks:
| Module | Role |
|---|---|
index.py |
FTS5 index over the KB markdown corpus |
query_expansion.py |
synonym and acronym expansion |
cooccurrence.py |
corpus co-occurrence expansion, embedding free |
trigram.py |
fuzzy fallback for typos and partial identifiers |
embeddings.py |
optional local ONNX hybrid ranking, blended with BM25 |
embeddings.py is off by default. It requires the embeddings extra and KB_EMBEDDINGS_MODE, imports its libraries lazily, and never calls an external API at query time. With the extra absent and the variable unset, the product is byte-for-byte unchanged. Do not describe this service as a vector or RAG pipeline: the default retrieval path is lexical.
Serving is server.py (MCP tools) and rest_api.py (the REST mirror). The enforcement surface is enforce_policy.py, write_gate.py, governed_lane.py, auth.py, principals.py, and rate_limit.py.
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 · 105 lines · 1,583 tokens per session scan A dfba17e75184
data-olympus AGENTS.md is an instructions file published in the GitHub repository knaisoma/data-olympus (23 stars, last pushed 23d ago), licensed Apache-2.0. It adds 1,583 tokens to every session, about $0.0079 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
hyalo CLAUDE.md
Claude Code instructions for ractive/hyalo, covering agents, documentation, dogfooding, rust and language server.
context CLAUDE.md
Claude Code instructions for Supa-Media/context, covering agent instructions — context, non-negotiables, architecture, the gateway (apps/mcp) and vocabulary.
Hatchdoor AGENTS.md
AGENTS.md instructions for BatterWorks/Hatchdoor, covering agent instructions, local-only instructions, running dev servers, dev vault fixtures and codegraph.
robust-llm-wiki CLAUDE.md
Instructions for KevinYoung-Kw/robust-llm-wiki, covering claude.md, the original karpathy baseline, made explicit and repository-specific policy.
llm-atomic-wiki CLAUDE.md
Claude Code instructions for cablate/llm-atomic-wiki, covering claude.md — schema for llms operating this repo, mental model, atom format (spec), frontmatter (yaml, required) and filename.
kaas CLAUDE.md
Instructions for bybit-exchange/kaas, covering claude.md, behavioral guidelines, 1. think before coding, 2. simplicity first and 3. surgical changes.