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/swarm-forge-crap)<a href="https://agentmods.dev/rules/leandropg19/memorys/swarm-forge-crap"><img src="https://agentmods.dev/badge/rules/leandropg19/memorys/swarm-forge-crap/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/swarm-forge-crap"><img src="https://agentmods.dev/badge/rules/leandropg19/memorys/swarm-forge-crap.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.00192 | $0.00192 |
| Opus 5.5 | $0.00077 | $0.00077 |
| Sonnet 5.5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
swarm-forge-crap 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
CRAP
Change Risk Anti-Patterns: complejidad ciclomática combinada con hueco de cobertura. El número lo imprime un script, no una opinión.
- SIL / piso:
scripts/crap-gate.sh(line coverageCRAP_MIN_LINE_COV, default 15%). Vive dentro demerge-gate.sh. - Diff:
scripts/quality-gate.sh(lizard sobrerust/srctocado). Puerta: ninguna función nueva por encima de CRAP 6; ninguna existente sube frente aHEAD. CC ≤ 4 orienta; no se parte una función de un solo trabajo para bajar el número.
El cleaner (mejorador) baja funciones que el script reporta.
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 · 14 lines · 192 tokens per session scan A b15fbf29e196
swarm-forge-crap is a cursor rule published in the GitHub repository LeandroPG19/Memorys (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 192 tokens to every session, about $0.0008 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-GoldenPayloadFixtures
AI rules for com.example.testing.GoldenPayloadFixtures.
com-example-testing-PaymentFixturesTest
AI rules for com.example.testing.PaymentFixturesTest.
testing-react
Testing React components — React Testing Library, hooks, context, async, accessibility. Extends core/rules/testing.mdc with React-specific patterns.
30-testing
Convenciones de testing, cobertura mínima, tipos de tests, mocks.
go
Go development guidelines — error handling, concurrency, interfaces, context propagation, and testing. Applied when working with Go code.
python
Python development guidelines — PEP 8, type hints, error handling, async patterns, packaging, and testing. Applied when working with Python code.