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/microsoft/agentic-agile-template/agents-mdgit clone --depth 1 https://github.com/microsoft/agentic-agile-templateWhat 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.02338 | $0.02338 |
| Opus 5 | $0.01169 | $0.01169 |
| Sonnet 5 | $0.00468 | $0.00468 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
agentic-agile-template 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 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.
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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[Project Name]
Universal agent entry point. Any agent reading this repository cold starts here. This file is both orientation reference and onboarding orchestrator.
What This Is
This repository is built on the Agentic-Agile Template — a starter framework for teams adopting structured human-agent collaboration. It provides the process layer that makes agent partnerships repeatable: structured backlogs, spec-first stories, platform adapter context files, built-in governance, and continuous measurement.
This file (AGENTS.md) is the single canonical entry point for all AI coding agents. Read it completely before taking any action in the repository. It detects which state the repository is in and routes you to the right starting point.
Repo Map
| Path | Purpose |
|---|---|
AGENTS.md |
This file. Universal agent entry point and onboarding orchestrator. |
README.md |
Human-facing project overview and getting-started guide. |
MANIFESTO.md |
The Agentic-Agile Manifesto: 5 values and 13 principles for human-agent development. |
STYLE.md |
Code conventions, commit message format, PR structure, documentation standards. |
CONTRIBUTING.md |
Human contribution workflow and PR guidelines. |
SECURITY.md |
Security policy and vulnerability reporting process. |
mcp.json |
Example MCP server configuration for agent tooling. |
platform-adapters/ |
Layered agent / tracker / CI-CD context. Three sub-layers: agent-tools/ (one adapter per AI agent), issue-trackers/ (one per backlog system), ci-cd/ (planned v2), plus combos/ for pre-assembled stacks. |
docs/agent-surface-selection.md |
Guide to choosing the right agent surface for different task types. |
docs/evaluation-framework.md |
Eight-dimension framework for measuring human-agent partnership effectiveness. |
docs/epic-decomposition-example.md |
Worked example: decompose an epic into stories, assign file ownership, plan waves. |
docs/history/ |
Implementation plan and design history (Phase 1/Phase 2 multi-platform generalization). |
.github/copilot-instructions.md |
GitHub Copilot-specific instruction file. |
.github/ISSUE_TEMPLATE/agentic-story.md |
Structured story template with scope, file ownership, and acceptance criteria. |
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 · 225 lines · 2,338 tokens per session scan A 6857d1b54682
agentic-agile-template AGENTS.md is an instructions file published in the GitHub repository microsoft/agentic-agile-template (88 stars, last pushed 2mo ago), licensed MIT. It adds 2,338 tokens to every session, about $0.0117 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-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.