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/LeandroPG19/MemorysWrote 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/leandropg19/memorys/testear-hasta-rojo)<a href="https://agentmods.dev/rules/leandropg19/memorys/testear-hasta-rojo"><img src="https://agentmods.dev/badge/rules/leandropg19/memorys/testear-hasta-rojo/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/leandropg19/memorys/testear-hasta-rojo"><img src="https://agentmods.dev/badge/rules/leandropg19/memorys/testear-hasta-rojo.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.00182 | $0.00182 |
| Opus 5.5 | $0.00073 | $0.00073 |
| Sonnet 5.5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
testear-hasta-rojo 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 22d 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
Testear hasta el rojo
- Primero el ancla de que el handler o la API está (MCP result / HTTP 200 / row count). Afirmar solo ausencia pasa igual sobre un corpus vacío.
skipyreturnsilencioso están prohibidos. Si falta el entorno, la corrida falla y lo dice. Sembrar el dato, no saltar.- Un test apagado no prueba nada.
#[ignore]solo existe porque el SIL los corre (cargo test -- --ignored). Un ignore que el gate no ejecuta es un skip silencioso. - Sabotear el assert, ver rojo, luego verde. Un test que nunca se puso rojo no está verificado.
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.
- 22d ago First seen · 12 lines · 182 tokens per session scan A ea5a997f068a
testear-hasta-rojo is a cursor rule published in the GitHub repository LeandroPG19/Memorys (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 182 tokens to every session, about $0.0007 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-09-24.
Other cursor rules, from other repositories
com-example-testing-PaymentFixturesTest
AI rules for com.example.testing.PaymentFixturesTest.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.