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/hyperb1iss/sibyl/claude-mdgit clone --depth 1 https://github.com/hyperb1iss/sibylWrote 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/hyperb1iss/sibyl/claude-md)<a href="https://agentmods.dev/instructions/hyperb1iss/sibyl/claude-md"><img src="https://agentmods.dev/badge/instructions/hyperb1iss/sibyl/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.02212 | $0.02212 |
| Opus 5 | $0.01106 | $0.01106 |
| Sonnet 5 | $0.00442 | $0.00442 |
| Haiku 4.5 | $0.00221 | $0.00221 |
Grade A, and why
sibyl 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sibyl Development Guide
Project Overview
Sibyl is a SurrealDB-native memory system - an MCP server and web app providing persistent memory, search, and task coordination through a unified graph, content, and auth runtime.
See package READMEs for detailed documentation:
README.md— Project overview, quickstart, philosophyapps/api/README.md— Server daemon (sibyld), MCP API, REST endpointsapps/cli/README.md— Client CLI (sibyl), user commandsapps/web/README.md— Web UI, components, React Query hookspackages/python/sibyl-core/README.md— Core library, models, graph client
Sibyl Integration
This project uses Sibyl as its own knowledge repository.
ALWAYS Use Skills
Use /sibyl for ALL Sibyl operations. This skill knows the correct patterns and handles
authentication properly.
/sibyl- Search, explore, add knowledge, manage tasks, project audits, sprint planning
Never call Sibyl MCP tools or CLI directly without going through a skill first.
Use /uv before running any uv commands. The skill provides current best practices and
prevents common mistakes.
- NEVER run
uv pip— it bypasses the project's dependency management. Useuv add,uv sync, oruv runinstead.
Research → Do → Reflect Cycle
Every significant task follows this cycle:
1. RESEARCH (before coding)
/sibyl search "topic"
/sibyl explore patterns
2. DO (while coding)
/sibyl task start <id>
3. REFLECT (after completing)
/sibyl task complete <id> --learnings "What I learned"
/sibyl add "Pattern Title" "What, why, how, caveats"
Quick Reference
Monorepo Structure
sibyl/
├── apps/
│ ├── api/ # sibyld - Server daemon (serve, worker, db)
│ ├── cli/ # sibyl - Client CLI (task, search, add, etc.)
│ ├── web/ # Next.js 16 frontend
│ └── e2e/ # End-to-end tests
├── packages/python/
│ └── sibyl-core/ # Shared library (models, graph, ai, retrieval, services)
├── skills/ # Claude Code skills
├── hooks/ # Claude Code context hooks
├── charts/ # Helm charts
├── infra/ # Ansible self-host + local compose
└── docs/ # Documentation site (VitePress)
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 · 266 lines · 2,212 tokens per session scan A 9d312a52ea60
sibyl CLAUDE.md is an instructions file published in the GitHub repository hyperb1iss/sibyl (57 stars, last pushed today), licensed Apache-2.0. It adds 2,212 tokens to every session, about $0.0111 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
remnic AGENTS.md
AGENTS.md instructions for joshuaswarren/remnic, covering remnic - agent guide, architecture boundaries (non-negotiable), upstream references, adapter implementation rules and openclaw compatibility window.
Dragon-Brain CLAUDE.md
Instructions for iikarus/Dragon-Brain, covering dragon brain — claude.md, the harness, audit remediation (april–may 2026, complete 2026-05-09), the lie this audit closed and the contract that matters now.
vellis AGENTS.md
Instructions for volantlabs/vellis, covering agents.md, repository purpose, startup checks, installing vellis for a user and model-first component workflow.
brainlayer AGENTS.md
Instructions for EtanHey/brainlayer, covering brainlayer — a letter from etan, brainlayer agent notes (operational), review guidelines, key paths and database.
TideMind AGENTS.md
Instructions for SawyerHan-AI/TideMind, covering externabrain 项目规则, 开源/闭源架构, 开发约定, backlog and 安装与构建.
dakera-cli CLAUDE.md
Instructions for Dakera-AI/dakera-cli, covering dakera-cli, key commands, architecture and conventions.