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/alanhuang168/ai-project-workflow/agents-mdgit clone --depth 1 https://github.com/AlanHuang168/AI-Project-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/alanhuang168/ai-project-workflow/agents-md)<a href="https://agentmods.dev/instructions/alanhuang168/ai-project-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/alanhuang168/ai-project-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.1 | $0.00227 | $0.00227 |
| Opus 5 | $0.00113 | $0.00113 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
AI-Project-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 6d 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.
What it actually says
AI Project Workflow
Workflow Stages
init -> prd -> hld -> sdd -> impl -> review -> deploy -> retro
Document Priority
PRD -> Architecture -> SDD -> Test Plan -> Code
Mandatory Rules
- Read the relevant Skill before starting a stage.
- Verify that required upstream artifacts exist and are not empty.
- Write every deliverable to the actual project files.
- Do not implement business behavior that is not defined in the approved SDD.
- Stop and ask the user when requirements are ambiguous.
- Never report unexecuted tests as passed.
- Report failed commands and incomplete work honestly.
- Do not run commit, push, merge, rebase, or force push without explicit user approval.
- Do not modify files outside the current task scope.
- Update
.ai-workflow/state.jsonafter a stage is completed.
Skill Location
core/skills/<stage>/SKILL.md
Completion Report
- Current stage
- Modified files
- Generated documents
- Commands executed
- Verification results
- Incomplete work
- Risks
- Next stage
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.
- 6d ago First seen · 38 lines · 227 tokens per session scan A 88ac252106e3
AI-Project-Workflow AGENTS.md is an instructions file published in the GitHub repository AlanHuang168/AI-Project-Workflow (27 stars, last pushed 1mo ago), licensed MIT. It adds 227 tokens to every session, about $0.0011 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
awesome-copilot-id AGENTS.md
AGENTS.md instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.
llm-safe-haven CLAUDE.md
Claude Code instructions for pleasedodisturb/llm-safe-haven, covering llm safe haven, what this is, project structure, tdd — non-negotiable (adopted 2026-08-17) and the contract.
hiveshare CLAUDE.md
Instructions for KB-perByte/hiveshare, covering hiveshare — claude.md, repo layout, build & run, key env vars (server) and naming: hive vs memory.
kleosrules AGENTS.md
AGENTS.md instructions for kleosr/kleosrules, covering agents.md — repository agent handbook, law, pack, skills (on demand) and workflows.
finding-unknowns-skills CLAUDE.md
Claude Code instructions for Neeeophytee/finding-unknowns-skills, covering repo notes, what ships, and the gate that decides, version lives in three manifests — move them together, files that must be edited together and shipped guidance is not this file.
coding-agent-safety-gate AGENTS.md
Instructions for ASER-ho/coding-agent-safety-gate, covering agents / 代理规则, 仓库类型 / repository type and ai 代理规则 / rules for ai coding agents.