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/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/quality)<a href="https://agentmods.dev/rules/m3taz-ahmed/ai-globals/quality"><img src="https://agentmods.dev/badge/rules/m3taz-ahmed/ai-globals/quality.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.1 | $0.00553 | $0.00553 |
| Opus 5 | $0.00277 | $0.00277 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
quality 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 7d 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
[FILE] quality.mdc [OBJ] Quality gates. [RULES]
- [REQ]
[CODE-01]Service-Repo separation. Thin controllers. - [REQ]
[CODE-02]Strict typing. Noany/mixed/unknownabuse. - [REQ]
[CODE-03]Class <300 lines, method <30 lines. - [REQ]
[CODE-04]Enums/constants over magic strings. - [REQ]
[CODE-05]SOLID & DRY. - [REQ]
[TEST-01]Mandatory coverage. - [REQ]
[TEST-02]AAA pattern. One behavior per test. - [REQ]
[TEST-03]Factories/seeders. No hardcoded IDs/dates. - [REQ]
[TEST-04]Pest 3+ (backend), Vitest+RTL (frontend), pytest (Python), go test (Go). - [REQ]
[TEST-06]80% logic, 90% API, 70% total coverage. - [REQ]
[TEST-07]Two-tier testing: FAST (targeted, ~5s, during iteration) + FULL (complete suite + coverage, before done). Seeworkflows/testing-tiers.md. - [REQ]
[TEST-08]Per-stack commands: PHPartisan test --filter=/artisan test; JSvitest run <file>/vitest run --coverage; Pythonpytest <file> --no-cov/pytest --cov; Gogo test <pkg> -short/go test ./... -cover. - [REQ]
[TEST-09]If no test framework exists, write the first test for touched code before done. - [REQ]
[TEST-10]Mark slow tests (E2E, integration, model-loading) with framework skip mechanism. Fast tier stays under 5s. - [PROHIBIT] No inline imports (
await import()). No downgrade deps for type errors. - [PROHIBIT] No
TODO/FIXMEwithout ticket tag. - [PROHIBIT] No full test suite on every change (use FAST tier). No skipping FULL tier before done.
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.
- 7d ago First seen · 27 lines · 553 tokens per session scan A ced3d3eef3fb
quality is a cursor rule published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 553 tokens to every session, about $0.0028 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
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.
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.