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 rules/phuoctrung-ppt/ai-sdlc-workflow/006-agentic-workflowgit 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/rules/phuoctrung-ppt/ai-sdlc-workflow/006-agentic-workflow)<a href="https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/006-agentic-workflow"><img src="https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/006-agentic-workflow.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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
006-agentic-workflow 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Workflow Guardrails
Canonical workflow: AGENTS.md. Project standards are configured in .cursor/config/workflow-policy.json and always include AGENTS.md.
Execution Order
- Classify the change mechanically with
.cursor/config/protected-paths.json; do not rely on agent self-report. - Plan with
architect-plannerfor protected module-spanning/high-risk work. - Implement with the narrowest matching worker agent.
- Verify locally with checks proportional to risk.
- For protected changes, persist
docs/reviews/*viajudge-agentor/workflow-evalbefore completion.
Protected Change Classifier
Protected status is shared by plans, judge review, stop hooks, and /workflow-eval:
- Path globs and keywords live in
.cursor/config/protected-paths.json. - Multi-file threshold also lives in
.cursor/config/protected-paths.json. - Fail closed only for protected changes. Fail open for standard changes to avoid team-wide lockouts from broken hooks.
/workflow-evalalways writes a durable review artifact whenever it runs.
Hook Enforcement
preToolUseenforces worker path scopes from.cursor/config/worker-scopes.json.afterFileEditrecords edited files for stop-hook classification.stopblocks protected changes without current plan/review artifacts.- Stop blocking has a retry cap; after the cap, the hook writes a human escalation artifact instead of looping forever.
- Manual review override must be explicit and logged with
.cursor/hooks/review-override.sh --skip-review "reason".
If scope enforcement blocks a worker, request scope expansion from the orchestrator with the path, reason, and updated acceptance criteria.
Handoff Packet Required
Every worker task should start from a handoff packet containing:
- Objective
- In-scope paths
- Out-of-scope paths
- Required skills and selected reference files
- Acceptance criteria
- Required verification commands
- Risks or constraints from
AGENTS.md
If any field is missing, infer only low-risk details from the codebase. Ask the orchestrator before expanding scope.
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 · 70 lines · 691 tokens per session scan A 8d26f0fbd09e
006-agentic-workflow is a cursor rule published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 17d ago), licensed MIT. It adds 691 tokens to every session, about $0.0035 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.