Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/mtnyilmaz/agents/claude-mdgit clone --depth 1 https://github.com/mtnyilmaz/agentsWrote 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/mtnyilmaz/agents/claude-md)<a href="https://agentmods.dev/instructions/mtnyilmaz/agents/claude-md"><img src="https://agentmods.dev/badge/instructions/mtnyilmaz/agents/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 | $0.00580 | $0.00580 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
agents 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 4d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Instructions
This is a centralized agent rules registry. See
README.mdfor the complete system overview.
What This Repo Is
A layered, multi-IDE AI agent rule system. Rules are organized in .agents/layers/ by scope (universal → language → framework → concern → project), assembled per-repo via install.sh, and synced to IDE tools via sync-rules.sh.
How to Work With This Repo
- Read
README.mdfor the full system overview - Rules source of truth:
.agents/layers/ - Skills:
.agents/skills/ - Workflows:
.agents/workflows/ - Scripts:
.agents/scripts/install.shandsync-rules.sh
Installing Rules Into a Target Repo
bash .agents/scripts/install.sh --type <type> --target /path/to/repo
bash .agents/scripts/sync-rules.sh # run inside target repo
Supported --type values: nextjs, nuxt, vue, react, tanstack, fastify, express, go, django, fastapi, laravel, expo, email-*, fullstack
Layer Order
universal → language → framework → concern → project
Each layer narrows scope. universal applies to every repo. project applies only to one specific repo.
Critical Rules (apply everywhere)
- Never commit without explicit user permission
- Conventional Commits:
feat(scope): description - Adapter pattern for all third-party integrations
- Soft delete everywhere — never hard delete records
- No
console.login production code — use structured logger - Route → Service → Database — never skip service layer
- User-facing copy (any app name in the repo): always from that package’s i18n — default
en, standard secondtr; no hardcoded client-visible literals (dummy/fixture/seed/test data excepted)
Version Policy (MANDATORY)
ALWAYS use @latest when installing any dependency. Never rely on your training data for version numbers — they are outdated. Never copy version numbers from rule/skill/layer files.
# RIGHT — always @latest
npx create-next-app@latest
npx create-expo-app@latest
pnpm add next@latest fastify@latest expo@latest zod@latest
# WRONG — never hardcode versions
npx create-next-app@15 # ❌
pnpm add fastify@5 # ❌
pnpm add expo@54 # ❌
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.
- 4d ago First seen · 61 lines · 580 tokens per session scan A 3fee608c68da
agents CLAUDE.md is an instructions file published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 580 tokens to every session, about $0.0029 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.