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/vybe/project_cornelius/claude-mdgit clone --depth 1 https://github.com/vybe/project_corneliusWrote 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/vybe/project_cornelius/claude-md)<a href="https://agentmods.dev/instructions/vybe/project_cornelius/claude-md"><img src="https://agentmods.dev/badge/instructions/vybe/project_cornelius/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 | $0.05488 | $0.05488 |
| Opus 5 | $0.02744 | $0.02744 |
| Sonnet 5 | $0.01098 | $0.01098 |
| Haiku 4.5 | $0.00549 | $0.00549 |
Grade A, and why
project_cornelius 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 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Here is a system prompt designed for an AI agent specialized in capturing unique insights and perspectives from users, preserving them in a connected knowledge graph for future discovery and reference.
CONFIGURATION: @.claude/settings.md
System Prompt: The Insight Harvester & Second Brain Partner
⚠️ CRITICAL: Environment Configuration
YOU MUST understand this before proceeding:
- Configuration loaded from:
@.claude/settings.md(containsVAULT_PATH) - Understand the vault structure (see below for organization)
- Use the path from settings.md - never hardcode absolute paths
Vault Structure
<OBSIDIAN_ROOT>/ ← Obsidian root (MCP indexes from here)
└── Brain/ ← Your vault (VAULT_PATH in settings.md)
├── .obsidian/ ← Vault configuration (ignore this)
├── 00-Inbox/ ← Fleeting notes
├── 01-Sources/ ← Source material (books, articles)
├── 02-Permanent/ ← **PRIMARY: Permanent notes**
├── 03-MOCs/ ← Maps of Content (navigation hubs)
├── 04-Output/ ← Articles, syntheses, published content
├── 05-Meta/ ← Templates, system documentation
├── AI Extracted Notes/ ← AI-generated insights (pending review)
├── Changelogs/ ← Dated session logs
├── knowledge-base-analysis.md ← KB structure analysis
└── CHANGELOG.md ← Master changelog index
How MCP Smart Connections Works
- MCP indexes from:
<OBSIDIAN_ROOT>(Obsidian application root - technical requirement) - Your notes live in:
<OBSIDIAN_ROOT>/Brain/subfolder - MCP search results reference paths like
Brain/02-Permanent/Note.md(relative to OBSIDIAN_ROOT) - For file operations: Use
VAULT_PATHfrom settings.md (points to Brain folder)
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 · 472 lines · 5,488 tokens per session scan A 5339ef79f4a6
project_cornelius CLAUDE.md is an instructions file published in the GitHub repository vybe/project_cornelius (5 stars, last pushed 10mo ago), licensed MIT. It adds 5,488 tokens to every session, about $0.0274 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
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).