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/chand1012/cursorrules/soliditygit clone --depth 1 https://github.com/chand1012/cursorrulesWhat 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.01124 |
| Opus 5 | $0.00000 | $0.00562 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
solidity 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solidity Foundry Development Best Practices
This document provides guidelines for writing smart contracts in Solidity using the Foundry framework. It adapts concepts from TypeScript best practices to suit Solidity's unique type system, execution environment, and Foundry's tooling.
Type System
- Use interfaces to define function signatures for external contract interactions (e.g., ERC20 interfaces).
- Prefer structs to group related data into a single unit (e.g.,
struct User { address addr; uint256 balance; }). - Use enums to represent discrete states or options (e.g.,
enum Status { Pending, Active, Closed }). - Leverage mappings for efficient key-value storage (e.g.,
mapping(address => uint256) balances). - Use custom types (Solidity 0.8.8+) for clarity and type safety (e.g.,
type UserId is uint256;).
Naming Conventions
- Use PascalCase for contract, struct, enum, and interface names (e.g.,
MyContract,UserStruct). - Use camelCase for function and variable names (e.g.,
transferFunds,userBalance). - Use UPPER_CASE for constants (e.g.,
MAX_SUPPLY,FEE_PERCENT). - Use descriptive names with auxiliary verbs where applicable (e.g.,
isPaused,hasRole). - Prefix events with
Logfor clarity (e.g.,event LogTransfer(address from, address to, uint256 amount)).
Code Organization
- Follow Foundry's default project structure:
src/for smart contracts.test/for test files (use.t.solsuffix for test contracts).script/for deployment and interaction scripts written in Solidity.lib/for external dependencies (managed as git submodules).
- Keep related contracts in the same file or directory for logical grouping.
- Use libraries for reusable code (e.g., math operations, string utilities).
- Organize imports at the top of the file, grouped by source (e.g., local files, OpenZeppelin contracts).
- Include an SPDX license identifier at the top of each file (e.g.,
// SPDX-License-Identifier: MIT).
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 · 72 lines · 1,124 tokens per session scan A c8ff79939d9e
solidity is a cursor rule published in the GitHub repository chand1012/cursorrules (13 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,124 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-30.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.