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/appydave/appydave-tools/cursorrulesgit clone --depth 1 https://github.com/appydave/appydave-toolsWrote 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/appydave/appydave-tools/cursorrules)<a href="https://agentmods.dev/rules/appydave/appydave-tools/cursorrules"><img src="https://agentmods.dev/badge/rules/appydave/appydave-tools/cursorrules.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.00033 | $0.00033 |
| Opus 5 | $0.00016 | $0.00016 |
| Sonnet 5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00003 | $0.00003 |
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 yesterday.
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
When working with ruby files:
- All ruby files should start with # frozen_string_literal: true
When working with unit tests
- Do not include requires
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.
- yesterday First seen · 6 lines · 33 tokens per session scan A 28d743d24da8
cursorrules is a cursor rule published in the GitHub repository appydave/appydave-tools (9 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session, about $0.0002 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-09-05.
Other cursor rules, from other repositories
rspec-let-do-blocks
Cursor rule "rspec-let-do-blocks" from panozzaj/cursor-rules, covering multi-line array, multi-line method call with keyword args, multi-line hash definition, complex single line expression and using { ... } for multi-line blocks.
specs
RSpec-specific rules for Ruby on Rails projects.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
yaxunit_test_writer_prompt
Ты — опытный разработчик 1С, специализирующийся на создании модульных и сценарных тестов с использованием фреймворка YAxUnit. Твоя задача — писать чистые, читаемые и надежные тесты для проверки бизнес-логики и программных интерфейсов в конфигурациях 1С. Ты должен генерировать только код теста в формате BSL. Никаких…
ruby-style
Ruby coding style aligned with project RuboCop config.
workato-connector-sdk
Cursor rule "workato-connector-sdk" from rkawaishi/workato-dev-kit, covering workato connector sdk (connector.rb), file structure, top-level structure of connector.rb, authorization types and required keys for an action.