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/iloveitaly/llm-ide-rulesWrote 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/iloveitaly/llm-ide-rules/frontend-tests)<a href="https://agentmods.dev/rules/iloveitaly/llm-ide-rules/frontend-tests"><img src="https://agentmods.dev/badge/rules/iloveitaly/llm-ide-rules/frontend-tests/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/iloveitaly/llm-ide-rules/frontend-tests"><img src="https://agentmods.dev/badge/rules/iloveitaly/llm-ide-rules/frontend-tests.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.00054 | $0.00054 |
| Opus 5.5 | $0.00022 | $0.00022 |
| Sonnet 5.5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
frontend-tests 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 21d 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
Frontend Tests
- Do not add unit tests that duplicate Playwright coverage. Only add unit tests for edge cases which are not covered by Playwright.
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.
- 21d ago Changed · -1 lines 2d7cfc5f2375
- 27d ago First seen · 10 lines · 54 tokens per session scan A ff88e23db000
frontend-tests is a cursor rule published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed today), licensed MIT. It adds 54 tokens to every session, about $0.0002 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-19.
Other cursor rules, from other repositories
testing-patterns
Testing patterns and best practices for PRPM codebase with Vitest.
cursor-rules
Playwright E2E testing rules for {{PROJECTNAME}}; the full skill lives in .agents/skills/playwright-e2e.
playwright-e2e-testing
E2E testing with Playwright.
playwright-integration-testing-cursorrules-prompt-file
Cursor rules for Playwright development with integration testing.
cursor-rule
This is a test rule for PRPM integration testing.
roslyn-mcp-tools
MCP tool mapping — skeleton vs decompile vs symbols vs build.