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.
git clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsWrote 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/qwickapps/ai-sdlc-workflows/common-patterns)<a href="https://agentmods.dev/rules/qwickapps/ai-sdlc-workflows/common-patterns"><img src="https://agentmods.dev/badge/rules/qwickapps/ai-sdlc-workflows/common-patterns/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/qwickapps/ai-sdlc-workflows/common-patterns"><img src="https://agentmods.dev/badge/rules/qwickapps/ai-sdlc-workflows/common-patterns.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.02050 | $0.02050 |
| Opus 5.5 | $0.00820 | $0.00820 |
| Sonnet 5.5 | $0.00410 | $0.00410 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
COMMON-PATTERNS 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.
How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Common Patterns Reference
When to apply: Understanding shared concepts used across all rule files.
Core Shared Concepts
This file consolidates patterns used across VALIDATION-GATES, COMMUNICATION-PROTOCOL, RESEARCH-DEPTH, WORKTREE-ENFORCEMENT, FACT-VERIFICATION, INVESTIGATION-METHODS, ITERATION-GATES, SATISFACTORY-CRITERIA, and WRITING-STYLE.
1. Evidence Requirements
File:Line Reference Format
Standard format:
file.js:42 # Single line
file.js:42-45 # Line range
src/migrations/index.ts:137 # Absolute from project root
When required:
- All factual claims about code
- Bug locations
- Implementation references
- Configuration changes
Example:
✅ "Migration fails at readMigrationFiles (payload.config.ts:137)"
❌ "Migration fails in the config file"
Evidence Components
Every claim needs these 4 elements:
-
Source: Where the information comes from
- File path with line numbers
- URL to documentation
- Command output
-
Evidence: Actual proof
- Code snippet
- Documentation quote
- Test result
- Screenshot (rare)
-
Verification method: How you confirmed it
- "Code inspection"
- "WebFetch of documentation"
- "Tested on clean database"
- "Used Explore agent"
-
Context: Version/date when relevant
- Package version
- Commit hash
- Date of check
- Platform version
2. Checklist Usage Pattern
Standard Checkbox Format
- [ ] Item to verify
- [ ] Another item to check
- [ ] Third verification point
How to Use Checklists
Before proceeding:
- Read each checkbox item
- Verify it's complete/true
- Mentally check it off
- If ANY fails, stop and fix it
Common mistake:
- Skipping checklist items
- Assuming items pass without checking
- Proceeding when checkboxes fail
Correct approach:
- Actually verify each item
- Fix failures before proceeding
- Document why skipped (if approved)
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 · 397 lines · 2,050 tokens per session scan A 1b90d90028e9
COMMON-PATTERNS is a cursor rule published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 2,050 tokens to every session, about $0.0082 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.