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.
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-angular-chrome-devtools-testing-shortgit clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWhat 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 | $0.00271 | $0.00271 |
| Opus 5 | $0.00135 | $0.00135 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
modus-angular-chrome-devtools-testing-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 2d 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
Chrome DevTools Testing - Short
Mandatory Chrome DevTools MCP usage for comprehensive Angular + 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 HTML structure and component rendering
- Test interactive elements - Verify Modus Web Components work correctly
- Performance testing - Use DevTools for performance analysis
- Test all 6 themes - Verify components work in all Modus themes
Testing Checklist
- No console errors or warnings
- Components render correctly
- Events fire and handle properly
- Forms validate correctly
- Modals open/close with native dialog API
- All 6 themes display correctly
- Keyboard navigation works
- Accessibility attributes present
Reference
For detailed testing workflows and checklists, fetch the full rule: modus-angular-chrome-devtools-testing
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.
- 2d ago First seen · 35 lines · 271 tokens per session scan A 2e92145777a4
modus-angular-chrome-devtools-testing-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It adds 271 tokens to every session, about $0.0014 per session on Opus 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-08-31.
Other cursor rules, from other repositories
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
playwright-agents
../../templates/cursor-rules/playwright-agents.mdc.
qa-script-executor
QA Script Executor - Executes natural language test scripts using Chrome DevTools MCP and enhances them with technical hints.
playwright
本规范强制执行 Playwright 测试的最佳实践和编码标准，包括稳定的选择器、测试隔离、以用户为中心的测试和性能考虑。.
cursorrule
A Model Context Protocol (MCP) server for automating Playwright tests.