Borrowing it
Nothing to install: this file belongs to domondi1/inferrail. 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/domondi1/inferrail/main/CLAUDE.mdgit clone --depth 1 https://github.com/domondi1/inferrailWrote 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/domondi1/inferrail/claude-md)<a href="https://agentmods.dev/instructions/domondi1/inferrail/claude-md"><img src="https://agentmods.dev/badge/instructions/domondi1/inferrail/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.1 | $0.00802 | $0.00802 |
| Opus 5 | $0.00401 | $0.00401 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
inferrail 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 yesterday.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inferrail — Agent Context
Inferrail is an open inference control plane: an OpenAI-compatible
gateway that sits between an application and the model providers it
calls. v0.1 today is the gateway only. See docs/PRODUCT.md for
exact current scope and docs/ARCHITECTURE.md for how it's built.
Before major feature work, read
docs/PRODUCT.md— authoritative source for exact current scope: what works, what's explicitly not supported yetdocs/ARCHITECTURE.md— package layout, request lifecycle, and the boundaries (provider, routing, telemetry, data-plane/control-plane) that keep the codebase easy to extenddocs/PRINCIPLES.md— the durable engineering principles behind this projectdocs/adr/— architecture decision records for specific structural choices
Before implementing something substantial, ask
- Which problem does this change solve?
- Does it match a principle in
docs/PRINCIPLES.md, or does it conflict with one? - Is there a smaller implementation?
- Does
docs/PRODUCT.mdneed to change alongside the code, so scope stays accurate? - What test proves this works?
Engineering rules
- Exact current scope must match the code. If a feature ships or a
non-goal changes, update
docs/PRODUCT.mdin the same change. - No prompt/response payload persistence in telemetry by default — this is a schema-level guarantee, not a runtime flag.
- No secret or silent telemetry — nothing leaves the machine unless a sink is explicitly configured to do that, and it must be documented.
- No fabricated metrics. Values that can't be measured trustworthily
(cost, time-to-first-token, etc.) stay
null— never estimated or guessed. - The OSS data plane must keep working with zero dependency on any Inferrail-operated service.
- Prefer deterministic, testable behavior — keep the core engine independent of the web framework so it can be tested without an HTTP server.
- Keep the hot request-execution path small; avoid unnecessary dependencies and speculative complexity.
- Clearly distinguish shipped features from future work — a missing capability is a documented non-goal, not a silent gap.
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.
- yesterday Changed · +13 lines · +162 tokens per session 8822aa47bf0a
- 7d ago First seen · 63 lines · 640 tokens per session scan A 3efdc398a0a4
inferrail CLAUDE.md is an instructions file published in the GitHub repository domondi1/inferrail (0 stars, last pushed today), licensed Apache-2.0. It adds 802 tokens to every session, about $0.0040 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).
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).
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.
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.