Borrowing it
Nothing to install: this file belongs to korenmiklos/CLAUDE.md. 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/korenmiklos/CLAUDE.md/main/AGENTS.mdgit clone --depth 1 https://github.com/korenmiklos/CLAUDE.mdWrote 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/korenmiklos/claude.md/agents-md)<a href="https://agentmods.dev/instructions/korenmiklos/claude.md/agents-md"><img src="https://agentmods.dev/badge/instructions/korenmiklos/claude.md/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.1 | $0.02267 | $0.02267 |
| Opus 5 | $0.01133 | $0.01133 |
| Sonnet 5 | $0.00453 | $0.00453 |
| Haiku 4.5 | $0.00227 | $0.00227 |
Grade A, and why
CLAUDE.md 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 6d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides global user preferences and guidance to AI coding agents when working with code on this system.
Software tools
Shell (mandatory)
All scripts should be runnable from the command line. The default shell of the user is fish, but scripts should be compatible with bash as well. All scripts are called from the root of the folder, and relative paths should be used to refer to files in subfolders.
Make (mandatory)
A single Makefile in the root of the folder should be used to run all scripts. The Makefile should have targets for each major step in the workflow, such as data wrangling, analysis, and reporting. Don't use Makefile as a script, but as a build tool: how to build the target from source using a recipe. For analytics, targets are data or research artifacts, sources are scripts and other data artifacts. For example, temp/clean_data.csv: code/create/clean.py input/raw/data.csv with the recipe python $<.
Bead (mandatory)
External data dependencies are managed by bead. Metadata is stored in .bead-meta/ subfolder. Input datasets are in input/ subfolder. Use bead input load <name> for missing data and bead input update <name> for updates. The temp/ subfolder is for temporary files, output/ for final output files. Check documentation at https://context7.com/bead-project/bead/llms.txt?tokens=10000
git (mandatory)
The folder is under version control with git. .gitignore should reflect the set of software tools used. Because bead is always used, .gitignore should always include input/ and temp/ folders. Avoid using git add . as this can include files that are not to be shared. Instead, add the files that have changed explicitly by name.
NEVER use git add -f to override .gitignore without explicit user permission. Files in .gitignore are there to:
• Protect sensitive data (credentials, private notes, proprietary data) • Exclude build artifacts and temporary files • Maintain repository hygiene
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.
- 6d ago First seen · 154 lines · 2,267 tokens per session scan A d9ef756189fc
CLAUDE.md AGENTS.md is an instructions file published in the GitHub repository korenmiklos/CLAUDE.md (2 stars, last pushed 9mo ago), licensed MIT. It adds 2,267 tokens to every session, about $0.0113 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.