Borrowing it
Nothing to install: this file belongs to abhilash-m96/agentic-coding-workflow. 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/abhilash-m96/agentic-coding-workflow/main/AGENTS.mdgit clone --depth 1 https://github.com/abhilash-m96/agentic-coding-workflowWrote 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/abhilash-m96/agentic-coding-workflow/agents-md)<a href="https://agentmods.dev/instructions/abhilash-m96/agentic-coding-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/abhilash-m96/agentic-coding-workflow/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/abhilash-m96/agentic-coding-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/abhilash-m96/agentic-coding-workflow/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01342 | $0.01342 |
| Opus 5.5 | $0.00537 | $0.00537 |
| Sonnet 5.5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
agentic-coding-workflow 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 2mo 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Coding Workflow:
Rules
- Never write code before the chunk plan is proposed, reviewed, and approved by the human and persisted to FEATURE_PLAN.md.
- One branch = one concern. No exceptions.
- Branches must be stacked on each other - not all branching off
main. - If a chunk feels too big, split it further.
- Verify git-town is installed before starting:
git town --version. If not installed, prompt for installing it. - FEATURE_PLAN.md is your source of truth. Re-read it at the start of every chunk.
Step 1 — Understand the Full Scope
- Read the full feature requirement before doing anything.
- Identify every change needed end-to-end.
- Do not write a single line of code until the full scope is clear.
Step 2 — Propose the Chunk Plan
Break the feature into small, logical, ordered layers and present them to the human for review.
Each chunk must:
- Represent exactly one concern
- Be independently readable and reviewable
- Build on top of the previous chunk
Example for a new REST API endpoint:
| Order | Branch | Contains |
|---|---|---|
| 1 | feat/db-schema |
Schema + migrations only |
| 2 | feat/validators |
Request/response validators only |
| 3 | feat/service-layer |
Business logic only |
| 4 | feat/controller |
Route handlers only |
Adapt to the nature of the work. This is an example, not a rigid template. Present your proposed chunks and wait for the human to confirm, adjust, or reject the plan before proceeding.
Step 3 — Write the Finalised Plan
Once the human approves the chunk plan, immediately write it to FEATURE_PLAN.md in the repo root:
# Feature Plan: <feature-name>
## Chunks
- [ ] feat/db-schema — Schema + migrations
- [ ] feat/validators — Request/response validators
- [ ] feat/service-layer — Business logic
- [ ] feat/controller — Route handlers
- [ ] feat/tests — Tests
## Stack Hierarchy
feat/db-schema → main
feat/validators → feat/db-schema
feat/service-layer → feat/validators
feat/controller → feat/service-layer
feat/tests → feat/controller
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.
- 2mo ago First seen · 186 lines · 1,342 tokens per session scan A 30078683bb3e
agentic-coding-workflow AGENTS.md is an instructions file published in the GitHub repository abhilash-m96/agentic-coding-workflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,342 tokens to every session, about $0.0054 per session on Opus 5.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
ruleProb copilot-instructions.md
Instructions for canblmz1/ruleProb, a project described as: Test whether your CLAUDE.md, AGENTS.md and .cursor/rules actually survive AI agent execution. Extract rules, generate sandbox scenarios, score compliance.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).