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/001-workflow-v2git 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/001-workflow-v2)<a href="https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/001-workflow-v2"><img src="https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/001-workflow-v2.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.00379 | $0.00379 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
001-workflow-v2 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.
What it actually says
Workflow Rules (V2)
Canonical workflow: AGENTS.md + .cursor/config/workflow-policy.json. Project memory: .memory/ (not full AGENTS.md on every turn).
Protected Changes
Classifier: .cursor/config/protected-paths.json. Fail closed only for protected paths.
- Plan artifact required:
docs/plans/**ordocs/adr/** - Review artifact required:
docs/reviews/** - Override:
.cursor/hooks/review-override.sh --skip-review "reason"
Hooks
preToolUse— worker path scopes fromworker-scopes.jsonstop— blocks protected changes without current plan/review- Session start — use context-builder, not legacy skill-loader alone
Artifacts
| Type | Path |
|---|---|
| Plans | docs/plans/YYYY-MM-DD-feature.md (compact: ≤500 tokens body) |
| ADRs | docs/adr/NNNN-title.md |
| Reviews | docs/reviews/YYYY-MM-DD-desc.md (audit only — not injected as context) |
| Patterns | .cursor/patterns/ (Tier 3 — injected when triggered) |
| Handoffs | .cursor/context/handoffs/*.json |
Compact Plan Format
# Feature Name
**Goal:** one sentence | **Protected:** yes/no | **Agents:** a, b
## Constraints
(from .memory/constraints.md — do not duplicate AGENTS.md)
## Files
| Path | Action | Owner |
## Execution
1. agent: step
## Risks
- ...
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 · 53 lines · 379 tokens per session scan A e94088dd42dc
001-workflow-v2 is a cursor rule published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 18d ago), licensed MIT. It adds 379 tokens to every session, about $0.0019 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.