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/agents-mdgit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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.01811 | $0.01811 |
| Opus 5 | $0.00905 | $0.00905 |
| Sonnet 5 | $0.00362 | $0.00362 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
agents 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 2d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Instructions
This is a centralized agent rules registry. See
README.mdfor the full system overview.
What This Repo Is
A multi-IDE, multi-stack, multi-team AI agent rule system. It provides layered rules and skills that scale across different languages, frameworks, and AI tools.
How to Use
# Auto-detect repo type from package.json / go.mod / composer.json / .agents/project.json:
bash .agents/scripts/install.sh --target /path/to/repo
# Or pass --type explicitly:
bash .agents/scripts/install.sh --type <type> --target /path/to/repo
# Supported types (framework names, not tech-stack labels):
# Frontend : nextjs nuxt vue react tanstack
# Backend : fastify express go django fastapi laravel
# Mobile : expo
# Email : email-react email-mjml email-maizzle
# Combined : fullstack (reads types[] from .agents/project.json)
# Opt-in addons (extra skill packs — not installed by default):
# --with-sast Installs 15 sast-* security-analysis skills
# Or persist in .agents/project.json: { "addons": ["sast"] }
# After install, sync to IDE tools
bash .agents/scripts/sync-rules.sh
Structure
.agents/
layers/ # Rule templates by scope (universal → language → framework → concern → project)
skills/ # Domain expert role files (go-developer, python-developer, etc.)
workflows/ # Multi-step procedures
scripts/ # install.sh + sync-rules.sh
Layer Hierarchy
| Layer | Applies to | Example files |
|---|---|---|
| universal | Every repo, every language | git-commit, security-baseline |
| language | TypeScript / Go / Python / PHP | types, testing, patterns |
| framework | Next.js / Nuxt / Fastify / Laravel / Django | app-router, patterns |
| concern | API / Frontend / Mobile / Email | rest-design, design-system, accessibility |
| project | This specific repo | architecture, naming, DB conventions |
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.
- 2d ago First seen · 124 lines · 1,811 tokens per session scan A 6dbcbfe5a395
agents AGENTS.md is an instructions file published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 1,811 tokens to every session, about $0.0091 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.