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/redhat-vmeperf/agent-tasks-template/sdlcgit clone --depth 1 https://github.com/redhat-vmeperf/agent-tasks-templateWhat 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.00038 | $0.00369 |
| Opus 5 | $0.00019 | $0.00185 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
sdlc 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 2d 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
SDLC Pipeline
This rule runs the 7-gate SDLC pipeline for software engineering tasks. Read .agents/pipelines/SDLC.md for the full pipeline process definition, gate definitions, escalation protocol, and all process rules.
Invocation
- "Run SDLC for [task]" — Start the full pipeline from Gate 1
- "Resume SDLC at gate N for [task]" — Resume the pipeline at Gate N
- "Jump to [gate name] for [task]" — Jump to a specific gate (architect, security-arch, team-lead, engineer, review, quality, audit)
- "Emergency SDLC for [incident]" — Expedited Chaotic-domain path (see Emergency Protocol in pipeline)
If the user does not provide a task description, ask them to describe the task.
SDLC Context
This pipeline produces code, tests, and inline documentation as its Gate 4 output.
- Gate 3 blocks: No code is written until Gate 3 is approved
- Gate 4 output: Implementation (code, tests, inline docs) + Implementation Report
- Gate 4 instruction: Write tests alongside the code, not after
- Gate 7 final action: MERGE / DEPLOY (human-approved)
Security
- Security steps cannot be skipped.
- No interaction with any service or system may reduce the security posture of data passing through the process (REQ-5).
- External context files must pass a security review before loading (REQ-6). See
.agents/SECURITY_REVIEW_CHECKLIST.md.
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.
- 2d ago First seen · 33 lines · 38 tokens per session scan A b13e6143c409
sdlc is a cursor rule published in the GitHub repository redhat-vmeperf/agent-tasks-template (3 stars, last pushed 4mo ago), licensed Unlicense. It adds 38 tokens to every session and 369 once invoked, about $0.0002 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.