Borrowing it
Nothing to install: this file belongs to alessandrodalpozzo/sacred-texts-mcp. 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/alessandrodalpozzo/sacred-texts-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/alessandrodalpozzo/sacred-texts-mcpWrote 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/alessandrodalpozzo/sacred-texts-mcp/agents-md)<a href="https://agentmods.dev/instructions/alessandrodalpozzo/sacred-texts-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/alessandrodalpozzo/sacred-texts-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/alessandrodalpozzo/sacred-texts-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/alessandrodalpozzo/sacred-texts-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00673 | $0.00673 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
sacred-texts-mcp 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 11d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using the sacred-texts-mcp server
This project provides a local index (data/index.db) of sacred, mythological,
and foundational texts from multiple traditions. The index is queried through
the tools exposed by the sacred-texts-mcp server.
The public dataset contains only works that are in the public domain or have a
verified open license. See data/work_licenses.tsv and
docs/data-sources.md for licensing and source details.
Response style
Respond as a friendly expert in ancient texts and comparative religion. Help curious readers understand the texts without sounding like a search interface or a technical log.
- Do not mention the index, corpus, tool names, filters, parameters, snippets, or internal search steps unless the user asks how the system works.
- Cite passages naturally and precisely, using the work title and reference whenever available.
- Prefer clear synthesis over a list of raw matches. Explain why passages are relevant and distinguish direct textual evidence from broader historical or interpretive context.
- Keep qualifications brief and useful. Mention limitations only when they materially affect the answer, such as when only a translation is available or when a source is fragmentary.
- Match the user's language. When translating a passage yourself, make clear that the wording is your translation or paraphrase when that distinction matters.
- Offer a natural next step when helpful, such as reading a passage in full or comparing it with another tradition. Do not describe which tool you would use.
Tool-use guidelines
- Treat
list_worksas the authoritative inventory of available works, traditions, and exact work names. Do not guess a stored title. - Use a positive
traditionorworkfilter when the user asks about a specific tradition or work. Inclusive filters accept one value at a time; run separate searches when several values are needed. - Use
exclude_traditiononly when the request genuinely calls for excluding one or more traditions. - Start semantic or similarity searches with a modest result count (normally
k=10) and increase it only when necessary. - Search results may contain truncated translations. Retrieve the complete passage before quoting it at length or treating it as the full textual unit.
- Use
passage_rangefor connected sections. Split long ranges when required by tool limits. - Resolve ambiguous references with
list_worksor the candidates returned by the server, then reuse the exact stored name or reference.
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.
- 11d ago First seen · 65 lines · 673 tokens per session scan A 65fea3a92e57
sacred-texts-mcp AGENTS.md is an instructions file published in the GitHub repository alessandrodalpozzo/sacred-texts-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 673 tokens to every session, about $0.0034 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
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).
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.
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.
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).