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/phuoctrung-ppt/ai-sdlc-workflow/agents-mdgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-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/phuoctrung-ppt/ai-sdlc-workflow/agents-md)<a href="https://agentmods.dev/instructions/phuoctrung-ppt/ai-sdlc-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/phuoctrung-ppt/ai-sdlc-workflow/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 | $0.03785 | $0.03785 |
| Opus 5 | $0.01893 | $0.01893 |
| Sonnet 5 | $0.00757 | $0.00757 |
| Haiku 4.5 | $0.00379 | $0.00379 |
Grade A, and why
ai-sdlc-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 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.
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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — <PROJECT_NAME>
TEMPLATE — DOMAIN-NEUTRAL. This repo ships the portable Planner-Worker-Judge workflow with no target domain. Replace every
<PLACEHOLDER>and every block tagged> _EXAMPLE_with your project's real values when you port this setup. Agents: if a section below is still a<PLACEHOLDER>, treat that fact as unknown — gather it from the codebase or ask the orchestrator. Never invent stack, structure, or compliance facts from an example block.
How to use this file: This is the canonical domain-config hub for the agentic workflow. Every agent reads this file at task start. Generic workflow rules, hooks, and skills live in
.cursor/and do not need editing when you port this setup to a new repo. Only this file and the config JSONs below need updating when adding new features:
.cursor/config/protected-paths.json→projectProtectedGlobs.cursor/config/worker-scopes.json→agentssection.cursor/skills/skills-manifest.v2.json→ add/remove domain skills
IMPORTANT : Always follow the development rules during the coding phase. See ./docs/development-rules.md.
1. Project Overview
| Field | Value |
|---|---|
| Project Name | <name> |
| Domain | <domain / industry> |
| Description | <one-sentence description of what the product does> |
| Monorepo | `<yes (tool: nx / turbo / pnpm-workspaces) |
| Multi-Tenancy | `<none |
2. Tech Stack (Locked — ADR required to change)
Fill one row per layer your project uses; delete rows that don't apply. State a version only when it is actually pinned. Once filled, changing a locked choice requires an ADR in
docs/adr/.
| Layer | Technology | Notes |
|---|---|---|
| Language | <e.g. TypeScript (strict)> |
|
| Backend framework | <...> |
|
| Frontend framework | <...> |
|
| Shared contracts | <schema/validation lib, e.g. Zod> |
source of truth for API types |
| Database | <...> |
|
| ORM / Migrations | <...> |
migrations only — no auto-sync |
| Cache / Queue | <...> |
|
| AI / LLM | `<provider(s) | none>` |
| Object storage | <...> |
|
| Auth | <...> |
|
| Email / Notifications | <...> |
|
| Payments | `<... | none>` |
| Infra / Deploy | <...> |
|
| Testing | <unit / integration / e2e frameworks> |
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 · 333 lines · 3,785 tokens per session scan A 45e6f8e32eae
ai-sdlc-workflow AGENTS.md is an instructions file published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 18d ago), licensed MIT. It adds 3,785 tokens to every session, about $0.0189 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.