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-testinggit 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.00000 | $0.00950 |
| Opus 5 | $0.00000 | $0.00475 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
modus-angular-chrome-devtools-testing 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.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome DevTools Testing - Angular + Vite
Comprehensive Chrome DevTools usage for Angular + Vite application 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
- Cross-browser validation - Test in Chrome, Firefox, Safari
Testing Workflow
1. Pre-Development Check
# Start development server
npm start
# Open browser at http://localhost:4200
2. Console Error Checking
Look for:
- JavaScript/TypeScript errors
- Angular warnings
- Modus Web Component initialization errors
- Network request failures
- CSP violations
3. DOM Inspection
Verify:
- Modus components render correctly
- Wrapper components pass props correctly
- Event listeners are attached
- Styles are applied correctly
4. Network Tab
Check:
- API requests complete successfully
- Fonts and icons load correctly
- No 404 errors for assets
5. Performance Testing
Monitor:
- Component render times
- Memory usage
- Change detection cycles
- Bundle size impact
Testing Checklist
Component Testing
- Component renders without console errors
- Props/inputs are passed correctly to Modus components
- Events emit correctly
- Styles match design system
- Accessibility attributes present
Form Testing
- Input values update correctly
- Validation errors display
- Form submission works
- Checkbox value inversion handled
Navigation Testing
- Routes work correctly
- Side navigation expands/collapses
- Menu items are accessible
- Active states highlight correctly
Theme Testing
- All 6 themes work correctly
- Theme switching persists
- Colors update appropriately
- No flash of unstyled content
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 · 186 lines · 0 tokens per session scan A bcd8c4685a9e
modus-angular-chrome-devtools-testing is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 950 tokens. 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
ui-testing
This guide covers UI testing practices and patterns specifically for the DuckDuckGo macOS browser.
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
050-testing
Reglas de testing — asegurar que el código funciona antes de operar con dinero real.
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.
cli-error-handling
CLI command error handling patterns.