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/chriswu727/sibyl/agents-mdgit clone --depth 1 https://github.com/chriswu727/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/chriswu727/sibyl/agents-md)<a href="https://agentmods.dev/instructions/chriswu727/sibyl/agents-md"><img src="https://agentmods.dev/badge/instructions/chriswu727/sibyl/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.01391 | $0.01391 |
| Opus 5 | $0.00696 | $0.00696 |
| Sonnet 5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
sibyl 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sibyl — Agent Guide
This file helps AI agents (Claude Code, Cursor, etc.) use Sibyl effectively via MCP.
Setup
pip install sibyl-research
# Optional local cross-encoder ranking:
pip install 'sibyl-research[rerank]'
# Optional experimental one-shot reports and report export:
pip install 'sibyl-research[report]'
# Retrieval-provider mode (recommended) needs NO key — you do the reasoning:
claude mcp add sibyl -- sibyl-mcp
# For the experimental research() tool, add a provider key so sibyl's own model runs it:
claude mcp add sibyl -e DEEPSEEK_API_KEY=sk-... -- sibyl-mcp --profile report
Core boundary — Sibyl retrieves, the host reasons
Recommended: YOU (the host model) research; sibyl only retrieves. This is keyless and gives the best quality, because YOUR reasoning is applied to real evidence — a mid-tier model doing the synthesis fabricates on hard questions, whereas you can cross-reference sources and abstain when they don't answer.
# structured retrieval for an agent pipeline (Loop/Argus-style):
gather_bundle("Serbian quarterfinalist 2018 Madrid Open men's singles")
→ consume ranked sources[].evidence[] passages; cite each by citation_id.
→ inspect content_origin; treat search_snippet evidence as a lead, not full text.
→ compare content_cluster_id; matching clusters are not independent corroboration.
→ inspect status and diagnostics before synthesis; relevance defaults to lexical_v1.
→ optional: ranker="flashrank"; inspect ranking_method and ranking_warning for fallback.
→ query_term_coverage is a recall hint, not proof of factual sufficiency.
→ quality_score=null means source quality has not been computed.
# readable retrieval for a conversational host:
gather_sources("Serbian quarterfinalist 2018 Madrid Open men's singles")
gather_sources("2018 Madrid Open men's singles draw results") # call again with sub-queries
→ read the returned [Source N] blocks, cross-reference, answer WITH citations.
→ if the sources don't contain it, gather more or say you don't know — never guess.
# bounded workflow for a dependent or multi-part question:
gather_evidence(question="In what year was the company that created CUDA founded?")
→ if next_action is decompose_query, call again with loop_id and one atomic query.
→ finish with the synthesis-ready supporting E-step IDs.
→ synthesize only after the loop status is ready; the host still does all reasoning.
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 · 138 lines · 1,391 tokens per session scan A e88bdb2ee874
sibyl AGENTS.md is an instructions file published in the GitHub repository chriswu727/sibyl (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,391 tokens to every session, about $0.0070 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
UltraRAG AGENTS.md
AGENTS.md instructions for OpenBMB/UltraRAG, covering agents.md, 1) project identity, 2) repository map (what matters most), 3) mental model of the system and 4) two-phase execution lifecycle.
DSHA AGENTS.md
AGENTS.md instructions for qiannianhuanxiang/DSHA, covering agents.md, 一句话, 技术约束(围绕这些设计), 分层与归属(改代码前先看这里) and 启动契约(不可破坏).
FastGPT AGENTS.md
AGENTS.md instructions for labring/FastGPT, covering agents.md, 项目概述, 设计文档, 架构 and packages (库代码).
ai-demo AGENTS.md
Instructions for symfony/ai-demo, covering agents.md, project overview, development commands, setup and vector store must be set up before indexing.
tuui AGENTS.md
Instructions for AI-QL/tuui, covering agents guidelines for this repository, 1. use the development server, not npm run build, 2. keep dependencies in sync, 3. coding conventions and 4. project structure.
graph-engineering-on-research AGENTS.md
AGENTS.md instructions for InjayTseng/graph-engineering-on-research, covering graph-engineering-on-research — agent bootstrap, 1. 身分, 2. 狀態(2026-09-01 實查), 3. 這個 repo 的規則是可執行的,不是散文 and 4. 跑起來與驗證.