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/logosdx/monorepo/quality-assurancegit clone --depth 1 https://github.com/logosdx/monorepoWrote 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/logosdx/monorepo/quality-assurance)<a href="https://agentmods.dev/rules/logosdx/monorepo/quality-assurance"><img src="https://agentmods.dev/badge/rules/logosdx/monorepo/quality-assurance.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.00016 | $0.01548 |
| Opus 5 | $0.00008 | $0.00774 |
| Sonnet 5 | $0.00003 | $0.00310 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
quality-assurance 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Assurance
Comprehensive standards for testing and documenting code to ensure quality and maintainability.
Documentation Structure
- Problem Statement - Why it exists, what problems it solves
- Core Philosophy - Design principles with examples
- Problem-Solving Examples - Real scenarios, not toy examples
- API Reference - Link to TypeDoc
- Advanced Patterns - Composition examples
/docs Directory Requirements
Primary focus: Answer "what is this?", "why does it exist?", and "when should I use this?"
- What is this? - Clear, concise description of the package/utility
- Why does it exist? - Problem statement with real-world context
- When should I use this? - Use cases and scenarios where this is the right choice
- Brief functionality showcase - Demonstrate key features with examples
- Link to TypeDoc - "How to use" details belong in JSDoc and generated TypeDoc
Documentation Patterns
- Always contrast: Show ❌ problematic vs ✅ good patterns
- Real-world context: Shopping carts, user data, not
foo/bar - Show @logosdx/utils: Demonstrate dogfooding in examples
- Include fallbacks: Error handling and graceful degradation
JSDoc Standards
- Document WHY, not just what the function does
- Always include @example with realistic usage
- Document error conditions and edge cases
- Internal APIs get
@internaltag
Test File Structure
- Mirror source structure:
tests/src/mirrorspackages/*/src/ - Relative imports: Use
../../../../packages/utils/src/index.tsnot@logosdx/utils - Required for tests: Relative imports validate actual implementation
- Use
mockHelperspattern withcalledExactlyfor consistent verification
Test Organization
- Group by functionality:
describe('flow-control: memo', () => {}) - Descriptive names:
"should [behavior] when [condition]" - Test all paths: Positive cases, error cases, edge cases
- Nest related tests in sub-describes
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 · 180 lines · 16 tokens per session scan A 9db6b55086b9
quality-assurance is a cursor rule published in the GitHub repository logosdx/monorepo (7 stars, last pushed 19d ago), licensed BSD-3-Clause. It adds 16 tokens to every session and 1,548 once invoked, about $0.0001 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.