Borrowing it
Nothing to install: this file belongs to inflexa-ai/inflexa. 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/inflexa-ai/inflexa/main/CLAUDE.mdgit clone --depth 1 https://github.com/inflexa-ai/inflexaWrote 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/inflexa-ai/inflexa/claude-md)<a href="https://agentmods.dev/instructions/inflexa-ai/inflexa/claude-md"><img src="https://agentmods.dev/badge/instructions/inflexa-ai/inflexa/claude-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/inflexa-ai/inflexa/claude-md"><img src="https://agentmods.dev/badge/instructions/inflexa-ai/inflexa/claude-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.03839 | $0.03839 |
| Opus 5 | $0.01920 | $0.01920 |
| Sonnet 5 | $0.00768 | $0.00768 |
| Haiku 4.5 | $0.00384 | $0.00384 |
Grade A, and why
inflexa 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Language
Write the git text, the GitHub text, and each document in ASD-STE100 Simplified Technical English (STE), issue 9.
Use STE in:
- each commit message
- each pull request: the title, the body, a comment, and a review
- each GitHub issue: the title, the body, and a comment
- each document in this project
STE does not apply to a chat reply, or to a comment in the code.
STE controls prose only. It does not control code, an identifier, a command, a tool name, or text that you copy from a file. Keep the copied text as it is.
Words
- Give one meaning and one part of speech to each word.
followmeans "come after". Useobeyfor a rule or an instruction. - Use one word for one thing each time. Do not change a term for style.
- Use a short, common word. Use
use, notutilize. Usestart, notinitiate. - Keep the articles
the,a, andan. Writeset the flag, notset flag. - Do not put more than three nouns together. Divide a longer group with
oforfor, or connect the related words with a hyphen. - Write a long technical name in full at the first occurrence. Then use a short form or an abbreviation.
- Do not use slang, an idiom, a metaphor, or a Latin abbreviation. Write
for example, note.g.. - Do not make a phrasal verb from approved words. Write
extinguish the fire, notput out the fire. Writerelease the fumes, notgive off the fumes. - Use American English spelling.
- Use gender-neutral words. Do not use
heorshe.
Verbs
- Use only these verb forms: the infinitive, the imperative, the simple present tense, the simple past tense, the simple future tense, and the past participle as an adjective.
- Do not use the perfect tenses. Do not use the progressive tenses. Write
the parser reads the file, notthe parser is reading the file. - Do not use an auxiliary verb to make a complex construction. Write
you can adjust the value, notthe value can be adjusted. - Use the active voice. In a description, use the passive voice only when the agent is unknown.
- Do not use the
-ingform as a verb or as an adjective. Writethe hook that runs, notthe running hook. An-ingword is permitted as a technical name, for exampleTestingorwelding torch. - Use a verb for an action, not a noun. Write
before you remove the unit, notbefore the removal of the unit. - If a word is approved as a noun only, add a verb. Write
do a check of the battery, notcheck the battery. - Use
mustfor a requirement. Do not useshallorshould. Usecanfor a possibility, notmay. - Do not write
mustbefore an imperative verb. Writedisconnect the hose, notyou must disconnect the hose. A warning is the exception.
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 First seen · 397 lines · 3,839 tokens per session scan A 053e8c78dac5
inflexa CLAUDE.md is an instructions file published in the GitHub repository inflexa-ai/inflexa (33 stars, last pushed today), licensed Apache-2.0. It adds 3,839 tokens to every session, about $0.0192 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-09-09.
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.
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.