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/memory-industry-gate)<a href="https://agentmods.dev/rules/leandropg19/memorys/memory-industry-gate"><img src="https://agentmods.dev/badge/rules/leandropg19/memorys/memory-industry-gate/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/memory-industry-gate"><img src="https://agentmods.dev/badge/rules/leandropg19/memorys/memory-industry-gate.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.00317 | $0.00317 |
| Opus 5.5 | $0.00127 | $0.00127 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
memory-industry-gate 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
Gate de MemoryIndustry
- Terminado =
./scripts/merge-gate.sh(o./scripts/como-el-ci.sh todo) en verde en este turno. Incluye--ignored, e2e sin soft-skip, deny, audit, crap-gate, mutants-gate. - GitHub Actions no es el juez. Excluye
MODEL_OR_CLI_ONLYy no tiene ONNX/NLI/reranker/LLM. front/backde Mapupita-Rust no existen aquí.cargo test --libno sustituye al SIL.- Antes de empujar: el mismo SIL.
como-el-ci.sh extra≡todo(no hay un extra más ligero). - Los comentarios se quedan (migraciones ≤0060, SHA-384, lecciones del gate).
- Migraciones publicadas hasta 0060 están congeladas. El fallo se arregla con una migración nueva.
- Los agentes no compilán ni cambian de rama en paralelo. Un
cargoa la vez. scripts/quality-gate.shse encadena después del SIL: lizard +cargo mutantsdel diff sobrerust/src. No sustituye amerge-gate.sh.- No junction de
.cursor/rulesal perfil: se perderían estas reglas.
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 · 17 lines · 317 tokens per session scan A 642015ccf894
memory-industry-gate is a cursor rule published in the GitHub repository LeandroPG19/Memorys (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 317 tokens to every session, about $0.0013 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
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.
com-example-testing-PaymentFixturesTest
AI rules for com.example.testing.PaymentFixturesTest.
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
quality
Quality tooling configuration and CI pipeline for the Composer plugin.
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.