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/logosdx/monoreponpx agentmods add rules/logosdx/monorepo/quality-assuranceWrote 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/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/logosdx/monorepo/quality-assurance"><img src="https://agentmods.dev/badge/rules/logosdx/monorepo/quality-assurance.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.00016 | $0.01548 |
| Opus 5.5 | $0.00006 | $0.00619 |
| Sonnet 5.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 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 — 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.
- 2mo 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 2d 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.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
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.