Borrowing it
Nothing to install: this file belongs to verdikta/verdikta-applications. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/verdikta/verdikta-applications/main/.cursorrulesgit clone --depth 1 https://github.com/verdikta/verdikta-applicationsWrote 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/verdikta/verdikta-applications/cursorrules)<a href="https://agentmods.dev/rules/verdikta/verdikta-applications/cursorrules"><img src="https://agentmods.dev/badge/rules/verdikta/verdikta-applications/cursorrules/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/verdikta/verdikta-applications/cursorrules"><img src="https://agentmods.dev/badge/rules/verdikta/verdikta-applications/cursorrules.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.00381 | $0.00381 |
| Opus 5.5 | $0.00152 | $0.00152 |
| Sonnet 5.5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
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 1mo 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
Verdikta Applications - General Development Rules
Project Overview
This is a monorepo containing Verdikta integration examples:
example-bounty-program/- AI-powered bounty/job system with IPFS integrationexample-frontend/- Reference implementation for Verdikta queriesdocs/- Documentation for the project
Key Principles
- Always look for existing code before creating new implementations
- Avoid duplication - check for similar functionality in the codebase
- Keep files under 200-300 lines - refactor when exceeding this
- Focus on relevant code - don't touch unrelated areas
- Test thoroughly - especially when changing core functionality
- Write clear documentation - update docs when adding features
Code Quality
- Use descriptive variable and function names
- Write modular and reusable components
- Implement comprehensive error handling
- Add input validation for all user inputs
- Follow existing patterns in the codebase
Environment Awareness
Write code that accounts for different environments:
dev- Development with verbose loggingtest- Testing with mock dataprod- Production with optimized settings
Before Making Changes
- Understand the existing implementation
- Check if similar functionality exists elsewhere
- Review related tests
- Consider impact on other parts of the system
- Update documentation if needed
When Fixing Bugs
- Understand why the test is failing
- Only change test logic if thoroughly convinced the test is wrong
- Prefer fixing implementation over changing tests
- Document the fix in comments if complex
Documentation Requirements
- Update README.md for user-facing features
- Update technical docs for architecture changes
- Add inline comments for complex logic
- Create guides for new workflows
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.
- 1mo ago First seen · 49 lines · 381 tokens per session scan A 909aca32ca9a
cursorrules is a cursor rule published in the GitHub repository verdikta/verdikta-applications (41 stars, last pushed today), licensed MIT. It adds 381 tokens to every session, about $0.0015 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-08-30.
Other cursor rules, from other repositories
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .