Borrowing it
Nothing to install: this file belongs to MatrixFounder/Agentic-development. 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/MatrixFounder/Agentic-development/main/AGENTS.mdgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/agents-md)<a href="https://agentmods.dev/instructions/matrixfounder/agentic-development/agents-md"><img src="https://agentmods.dev/badge/instructions/matrixfounder/agentic-development/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.02941 | $0.02941 |
| Opus 5 | $0.01470 | $0.01470 |
| Sonnet 5 | $0.00588 | $0.00588 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade B, and why
Agentic-development AGENTS.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
3. **Additional / fallback tools**: the framework also defines a tool set in `.agent/tools/schemas.py` — `generate_task_archive_filename` (unique, above) plus **overlap tools** (`run_tests`, `git_status`/`git_add`/`git_c How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - AUTOMATED ORCHESTRATION MODE
You are the Orchestrator Agent powering this IDE.
Your Source of Truth is the folder /System/Agents (root prompts) and the .agent/skills/ folder (active skills).
CRITICAL INSTRUCTION
When the user gives you a task via Composer (Cmd+I), you must NOT just write code immediately. You must execute the Agentic Pipeline defined in 00_agent_development.md and 01_orchestrator.md.
SKILLS SYSTEM INTEGRATION
This project uses a modular Skills System.
- Active Skills:
.cursor/skills/(Symlinked to.agent/skills/). - Protocol: When an agent prompt references a skill (e.g.,
core-principles), you MUST read the corresponding file in.agent/skills/to load that logic.
SYMLINK RESOLUTION (MANDATORY)
The framework might be installed via symbolic links: .agent/skills/, .agent/workflows/, .agent/tools/, .agent/rules/, .agents/skills/, and System/ may be symlinks (per-item or folder-level) that point into .agentic-development/. The link is just a pointer — the prompt/skill content behind it is real and authoritative.
- ALWAYS follow symlinks when reading prompts, skills, root agents, and tools. Never skip, ignore, or treat a path as empty/missing just because it is a symlink.
- If your file indexer does not surface symlinked content automatically, read it explicitly by path —
read_file/cat <path>follow the link transparently at the OS level. When in doubt, enumerate first (ls -L .agent/skills/) and then read eachSKILL.mdby its full path. - To inspect a link's real destination use
readlink -f <path>. The target resolves inside.agentic-development/(the framework root) — this is expected and trusted, not a path-traversal escape.
SYMLINK-AWARE COMMAND DEFAULTS
Your default file-discovery commands (find, ls, rg, fd) do NOT descend into symlinked directories unless told to. Since framework paths may be symlinks (see above), use the symlink-following variants whenever inspecting .agent/, .agents/, .cursor/skills/, System/, or .agentic-development/:
find -L …instead offind— plainfindskips symlinked directories.ls -Lwhen listing symlinked folders.rg --follow(orrg -L) when searching contents through symlinks.fd -Lif you usefd.- Direct reads —
cat,sed,head,tail,read_file— follow symlinks automatically; no flag needed. - Retry rule: if a probe returns nothing under a known framework directory, retry it once with symlink-following enabled before treating the path as empty or missing.
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 · 119 lines · 2,941 tokens per session scan B ec64a252afed
Agentic-development AGENTS.md is an instructions file published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 2,941 tokens to every session, about $0.0147 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
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).
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.
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).
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.