Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflownpx agentmods add rules/phuoctrung-ppt/ai-sdlc-workflow/000-coreWrote 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/000-core)<a href="https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/000-core"><img src="https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/000-core/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/rules/phuoctrung-ppt/ai-sdlc-workflow/000-core"><img src="https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/000-core.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.00383 | $0.00383 |
| Opus 5.5 | $0.00153 | $0.00153 |
| Sonnet 5.5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
000-core 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.
What it actually says
Core Rules (Workflow V2)
Execution Order
- Classify — run context-builder; obey Context Packet tiers
- Plan — architect-planner for protected or multi-module work
- Execute — narrowest worker from activation.agents
- Verify — checks proportional to risk
- Review — judge-agent for protected work or when reviewMode=required
Context Control (mandatory)
Before coding:
python3 .cursor/context/context-builder.py --task "$TASK" --agent <agent> [--paths ...] [--keywords ...]
- Read tier1 rules +
.memory/files — NOT fullAGENTS.md - Read tier2 skill SKILL.md entries only (1–2 for low complexity)
- Read tier3 patterns when listed
- Load tier4 references ONLY via
--expand-refor when in tier4.references - Never bulk-read
docs/reviews/, entirereferences/folders, or doNotLoad paths
Handoff Packet
Required before worker dispatch: objective, in-scope paths, out-of-scope paths, acceptance criteria, verification commands.
Machine-readable handoffs: .cursor/context/handoffs/*.json
Completion Evidence
- Modified files match acceptance criteria
- Lint/type/test/build run or skipped with concrete reason
- Docs/ADRs updated when behavior or architecture changed
- Protected changes have plan + review artifacts
Escalation
- Scope blocked → orchestrator with path, reason, updated acceptance
- Missing design spec → designer-worker (frontend UI)
- Architecture gap → architect-planner
- Security concern → security-worker
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 · 50 lines · 383 tokens per session scan A 01c1934365f5
000-core is a cursor rule published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (1 stars, last pushed 28d ago), licensed MIT. It adds 383 tokens to every session, about $0.0015 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.