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/damiansire/web-worker-patternsWrote 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/damiansire/web-worker-patterns/regla-de-oro)<a href="https://agentmods.dev/rules/damiansire/web-worker-patterns/regla-de-oro"><img src="https://agentmods.dev/badge/rules/damiansire/web-worker-patterns/regla-de-oro/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/damiansire/web-worker-patterns/regla-de-oro"><img src="https://agentmods.dev/badge/rules/damiansire/web-worker-patterns/regla-de-oro.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.00236 | $0.00236 |
| Opus 5.5 | $0.00094 | $0.00094 |
| Sonnet 5.5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
regla-de-oro 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 28d 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
- El dominio se escribe una vez en
core/; la presentación vive enthemes/, una entrada por theme registrado entheme.registry.ts(un theme puede reusar la presentación de otro, vermidnight.theme.ts, y solo cambiar su bloque de tokens). core/NUNCA importa dethemes/: la dependencia va en un solo sentido.- La lógica de Web Workers vive en
core/domain/workers/, nunca dentro de un theme. - Nada de colores/fuentes literales en componentes compartidos: siempre tokens semánticos
(
--surface,--ink,--accent,--thread-*). - Antes de cerrar un cambio:
npm run format:check,npm run build,npm test,npm run lint:boundaries. - Fuente de verdad completa:
ARQUITECTURA-multi-theme.md,CLAUDE.md,docs/AI-PROCESS.md,AGENTS.md.
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.
- 28d ago Changed · +2 lines · +39 tokens per session c5457ae53a2e
- 1mo ago First seen · 14 lines · 197 tokens per session scan A 661e5bd9f83b
regla-de-oro is a cursor rule published in the GitHub repository damiansire/web-worker-patterns (173 stars, last pushed 9d ago), licensed MIT. It adds 236 tokens to every session, about $0.0009 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-30.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
declarative-config
Prefer declarative configuration over hardcoded logic.