Borrowing it
Nothing to install: this file belongs to CRJFisher/ariadne. 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/CRJFisher/ariadne/main/AGENTS.mdgit clone --depth 1 https://github.com/CRJFisher/ariadneWrote 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/crjfisher/ariadne/agents-md)<a href="https://agentmods.dev/instructions/crjfisher/ariadne/agents-md"><img src="https://agentmods.dev/badge/instructions/crjfisher/ariadne/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/crjfisher/ariadne/agents-md"><img src="https://agentmods.dev/badge/instructions/crjfisher/ariadne/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.00727 | $0.00727 |
| Opus 5.5 | $0.00291 | $0.00291 |
| Sonnet 5.5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
ariadne 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 17d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidelines
Goals
- When refactoring, always investigate the existing information architecture beforehand. If the refactor will change the information architecture, then the refactor should include tasks to update and improve the information architecture.
- The information architecture should follow the DDD principles.
- Folders and file names should be expressive of the main, high-level action of the code within.
Project Layout / Intention Tree
- the top of the intention tree (the actual purpose of this codebase) is to detect call graphs and thereby find the entry point to the codebase.
- every change to the code needs to be justified in terms of its contribution to the top-level intention tree.
- the module layout is the instantiation of the intention tree.
- we never add 'extra' functionality outside of this intention tree, even if it is 'well-meaning' and 'might' be used one day. 'extra', surplus code reduces our longterm velocity. it is much better to spend effort reviewing narrow, focussed code and its integration, rather than trying to cover a wide surface area.
- all namings and documentation should only reflect the trunk and branches of the intention tree, not the 'differential' changes we make to the codebase. E.g. if we're changing 'method_resolution.ts', we don't just create a file like 'enhanced_method_resolution.ts', we just improve 'method_resolution.ts', leaving the core intention tree intact.
Refactoring Ethos
- DO NOT SUPPORT BACKWARD COMPATIBILITY - JUST CHANGE THE CODE.
Processing Pipeline
The core pipeline has three stages. Subsystem-specific guidance lives in .claude/rules/.
- Per-file indexing (
index_single_file/) — 4-pass semantic indexing: query tree → scopes → definitions → references - Project resolution (
project/+resolve_references/) — Registry updates, import location fixing, name resolution → call resolution - Entry point detection (
trace_call_graph/) — Build call graph, identify unreachable functions with language-specific filtering
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.
- 17d ago Changed · -182 lines · -1,263 tokens per session a803c90cf128
- 1mo ago First seen · 234 lines · 1,990 tokens per session scan A e35fe3d339ec
ariadne AGENTS.md is an instructions file published in the GitHub repository CRJFisher/ariadne (23 stars, last pushed 4d ago), licensed MIT. It adds 727 tokens to every session, about $0.0029 per session on Opus 5.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
weld copilot-instructions.md
Copilot instructions for configflux/weld: Use @docs/architecture/principles.md for architecture-sensitive changes.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).