Borrowing it
Nothing to install: this file belongs to sturlese/hippocampus. 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/sturlese/hippocampus/main/CLAUDE.mdgit clone --depth 1 https://github.com/sturlese/hippocampusWrote 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/sturlese/hippocampus/claude-md)<a href="https://agentmods.dev/instructions/sturlese/hippocampus/claude-md"><img src="https://agentmods.dev/badge/instructions/sturlese/hippocampus/claude-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.1 | $0.01570 | $0.01570 |
| Opus 5 | $0.00785 | $0.00785 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
hippocampus CLAUDE.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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hippocampus — a Claude Code–native Obsidian vault with Codex support
This directory is three things at once: a git repository, a Claude Code project,
and an Obsidian vault. The user drops messy notes into inbox/; the agent turns
them into a structured, cross-linked knowledge base under wiki/. Obsidian is
for browsing; Claude Code is the native interface and Codex is supported through
its AGENTS.md and skill adapters. This file is the canonical project contract
for both agents.
Layout
inbox/ Messy source notes, any format/language. IMMUTABLE: read, never edit.
inbox/_done/ Processed inbox files are MOVED here by the ingest skill (provenance).
wiki/ The structured knowledge base. Everything the agent writes lives here.
├── index.md Master catalog: one line per page. Update on every page create/rename.
├── log.md Append-only operations journal. New entries at the TOP. Never edit past entries.
├── hot.md Recent-context cache, ≤500 words. Overwrite completely each refresh.
├── sources/ One page per ingested source (type: source)
├── concepts/ Ideas, patterns, frameworks (type: concept)
├── entities/ People, orgs, products, tools (type: entity)
├── projects/ Ongoing personal/work projects (type: project)
├── notes/ Synthesis, decisions, saved sessions (type: note)
└── meta/ Lint reports, dashboards (type: meta)
_templates/ Canonical skeletons per note type. THE source of truth for page structure.
_attachments/ Images/PDFs referenced by wiki pages.
docs/ Framework documentation (upstream, part of the template). NOT vault content — never file notes here.
Frontmatter schema
Flat YAML only (no nested objects — Obsidian Properties requires flat). Universal fields, every page:
---
type: source | entity | concept | project | note | meta
title: "Human-Readable Title"
created: YYYY-MM-DD
updated: YYYY-MM-DD # bump on every content edit
tags: [lowercase, hierarchical/ok]
status: seed | developing | mature | evergreen
related: ["[[Other Page]]"] # wikilinks in YAML must be quoted
sources: ["[[Source Page]]"]
---
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.
- 6d ago First seen · 107 lines · 1,570 tokens per session scan A 9fd114081a96
hippocampus CLAUDE.md is an instructions file published in the GitHub repository sturlese/hippocampus (28 stars, last pushed 16d ago), licensed MIT. It adds 1,570 tokens to every session, about $0.0078 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.