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/julianoczkowski/create-trimble-appWrote 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/julianoczkowski/create-trimble-app/chrome-devtools-testing-solidjs-short)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/chrome-devtools-testing-solidjs-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/chrome-devtools-testing-solidjs-short.svg" alt="Measured on agentmods" 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.00193 | $0.00193 |
| Opus 5 | $0.00097 | $0.00097 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
chrome-devtools-testing-solidjs-short 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 4d 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.
This is a copy
89% identical to chrome-devtools-testing-react-short — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Chrome DevTools Testing - Short
Mandatory Chrome DevTools MCP usage for comprehensive SolidJS + Vite testing.
Key Rules
- Always use Chrome DevTools MCP - Never skip browser testing
- Test before completion - Validate all implementations in browser
- Check console for errors - Look for JavaScript errors and warnings
- Inspect DOM structure - Verify proper semantic HTML and component rendering
- Test interactive elements - Verify Modus Web Components work correctly
- Performance testing - Use DevTools for performance analysis
- Cross-browser validation - Test in Chrome, Firefox, Safari
Reference
For detailed testing workflows, patterns, and comprehensive checklists, fetch the full rule: chrome-devtools-testing-solidjs
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.
- 4d ago First seen · 24 lines · 193 tokens per session scan A f2c874a8032f
chrome-devtools-testing-solidjs-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 193 tokens to every session, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to chrome-devtools-testing-react-short, differing in 6 lines, and is treated as a copy.
Other cursor rules, from other repositories
ui-verification
UI layout checks before claiming work is done.
hatch3r-browser-verification
Playwright browser verification protocol for UI changes — spec-run-first invocation contract with non-launderable result tokens, exploratory snapshot-mode driving, and accessibility spot-checks.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
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.