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/amtiyo/agents/agents-mdgit clone --depth 1 https://github.com/amtiYo/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.02986 | $0.02986 |
| Opus 5 | $0.01493 | $0.01493 |
| Sonnet 5 | $0.00597 | $0.00597 |
| Haiku 4.5 | $0.00299 | $0.00299 |
Grade C, and why
agents AGENTS.md scanned grade C with 3 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
const codexConfig = '/Users/me/.codex/config.toml' Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Don't execute arbitrary code from config files Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
// Use spawnSync for external commands How it starts
The opening of the file, as written. The whole thing — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working on the @agents-dev/cli project.
Project Overview
@agents-dev/cli is a CLI tool that provides a practical standard layer for multi-LLM development. It solves the configuration fragmentation problem by syncing MCP servers, skills, and instructions across multiple AI coding tools (Codex, Claude Code, Gemini CLI, Cursor, Copilot, Antigravity) from a single source of truth.
Key Principle: One .agents/ folder syncs to all tools. Add an MCP server once, it appears everywhere.
Tech Stack
- Language: TypeScript (strict mode)
- Runtime: Node.js 20+
- Build: tsc (TypeScript compiler)
- Tests: Vitest
- CLI Framework: Commander.js
- Prompts: @clack/prompts
- Package Manager: npm
Project Structure
agents/
├── src/
│ ├── cli.ts # CLI entry point
│ ├── commands/ # Command implementations
│ │ ├── start.ts # Setup wizard
│ │ ├── sync.ts # Config sync
│ │ ├── mcp-add.ts # Add MCP server
│ │ └── ...
│ ├── core/ # Core logic
│ │ ├── sync.ts # Sync orchestration
│ │ ├── mcp.ts # MCP management
│ │ ├── renderers.ts # Tool-specific config generators
│ │ ├── trust.ts # Codex trust management
│ │ ├── ui.ts # CLI output helpers (colors, spinners)
│ │ └── ...
│ ├── integrations/ # Tool integrations
│ │ ├── codex.ts
│ │ ├── claude.ts
│ │ ├── cursor.ts
│ │ └── ...
│ └── types.ts # TypeScript types
├── tests/ # Test files
│ ├── *.test.ts # Unit tests
│ └── *.integration.test.ts # Integration tests
├── templates/ # Scaffold templates
│ └── agents/ # .agents/ directory templates
├── docs/ # Public documentation
└── bin/agents # CLI wrapper script
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.
- 3d ago First seen · 437 lines · 2,986 tokens per session scan C df4eca023b1a
agents AGENTS.md is an instructions file published in the GitHub repository amtiYo/agents (91 stars, last pushed 24d ago), licensed Apache-2.0. It adds 2,986 tokens to every session, about $0.0149 per session on Opus 5. A static security scan graded it C with 3 findings (reads agent configuration directories, unrestricted tool access, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.