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/piyushpathakqa/vigilis/cursorrulesgit clone --depth 1 https://github.com/piyushpathakqa/VigilisWhat 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.00204 | $0.00204 |
| Opus 5 | $0.00102 | $0.00102 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
cursorrules 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
Vigilis — Cursor context pointer
This is Vigilis, an agentic QA framework (Claude authors/generates/triages/self-heals Playwright tests; ships as an MCP server + CLI; gated in GitHub Actions).
Before doing anything, read these in order:
- AGENTS.md — fast orientation, conventions, commands
- docs/STATUS.md — current state, what's done, what's next, how to resume
- docs/DESIGN.md — architecture and the rationale behind every decision
- docs/ROADMAP.md — milestones M0–M4 mapped to Linear tickets TRE-22..45
Key conventions: TypeScript + ESM, pnpm workspaces, tsup build, Vitest, ESLint flat config. Verify with: pnpm lint && pnpm typecheck && pnpm test && pnpm build. Never claim done without running them. Current next task: TRE-30 (the sample-shop Next.js app).
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 · 15 lines · 204 tokens per session scan A 9f33ebb4cbac
cursorrules is a cursor rule published in the GitHub repository piyushpathakqa/Vigilis (5 stars, last pushed 13d ago), licensed MIT. It adds 204 tokens to every session, about $0.0010 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
ui-testing
This guide covers UI testing practices and patterns specifically for the DuckDuckGo macOS browser.
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
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.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.