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/savagelysubtle/BIG-BRAIN-Memory-BankWrote 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/savagelysubtle/big-brain-memory-bank/200-quality-verification-procedures)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/200-quality-verification-procedures"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/200-quality-verification-procedures/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/savagelysubtle/big-brain-memory-bank/200-quality-verification-procedures"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/200-quality-verification-procedures.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.00000 | $0.06023 |
| Opus 5 | $0.00000 | $0.03011 |
| Sonnet 5 | $0.00000 | $0.01205 |
| Haiku 4.5 | $0.00000 | $0.00602 |
Grade A, and why
200-quality-verification-procedures 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 9d 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 — 920 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: WHEN verifying design quality APPLY systematic procedures for validation globs: ["/*.md", "/*.mdc"] alwaysApply: true
TL;DR: The Quality Verification Procedures provide systematic processes for validating design solutions against requirements, quality standards, and best practices to ensure optimal outcomes.
1.0.0
1. **Requirements Validation**
- Systematic requirement coverage checking
- Completeness verification
- Correctness validation
- Consistency checking
- Traceability confirmation
2. **Standard Compliance**
- Design standard adherence verification
- Best practice alignment checking
- Pattern conformance validation
- Style guide compliance
- Convention adherence
3. **Quality Attribute Verification**
- Systematic quality attribute assessment
- Metric-based property validation
- Threshold satisfaction checking
- Target achievement verification
- Trade-off appropriateness
4. **Defect Detection**
- Design flaw identification
- Anti-pattern recognition
- Risk exposure assessment
- Vulnerability discovery
- Edge case handling verification
5. **Review Execution**
- Structured design reviews
- Expert assessment coordination
- Stakeholder validation
- Peer evaluation
- Cross-functional examination
These processes ensure comprehensive quality verification.
1. **Structural Validation**
- Component completeness
- Interface adequacy
- Relationship correctness
- Responsibility allocation
- Boundary appropriateness
2. **Architectural Style Analysis**
- Style adherence
- Style combination coherence
- Pattern application correctness
- Anti-pattern absence
- Style-requirement alignment
3. **Quality Scenario Evaluation**
- Scenario-based assessment
- Quality attribute response
- Trade-off appropriateness
- Growth scenario handling
- Change scenario support
4. **Risk Assessment**
- Architectural risk identification
- Technical debt detection
- Complexity hot spots
- Integration challenges
- Evolution limitations
5. **Stakeholder Concern Coverage**
- Viewpoint representation
- Stakeholder need alignment
- Priority reflection
- Constraint compliance
- Goal satisfaction
These procedures ensure architecture quality and appropriateness.
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.
- 9d ago First seen · 920 lines · 0 tokens per session scan A 605bca46474d
200-quality-verification-procedures is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,023 tokens. 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
components
Rules for component usage - which component libraries are allowed (shadcn/ui, Aceternity, Kibo, Magic UI, etc.), reuse over recreation, table implementation standards, and component modularization for both new features and existing components.
designer
Cursor rule "designer" from ulises-jeremias/agent-toolkit, covering designer, when invoked, design routing — canonical (do not run mechanically), figma subtree and delegate to skills.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.
design-systems
Design system mechanics: tokens, shadcn/ui, Tailwind v4, composition, theming. Load for UI implementation — aesthetics and anti-slop live in the anti-slop-design skill.
accessibility
Accessibility (a11y) rules for frontend components. Apply when editing UI or markup.
components
Component patterns and UI conventions.