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/bsv-blockchain/spv-wallet-go-client/cursorrulesgit clone --depth 1 https://github.com/bsv-blockchain/spv-wallet-go-clientWhat 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.00217 | $0.00217 |
| Opus 5 | $0.00109 | $0.00109 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
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
Cursor Rules derived from .github/AGENTS.md
Read AGENTS.md First
All contributors must read .github/AGENTS.md for complete guidelines. If any rule here conflicts with that file, AGENTS.md takes precedence.
Coding Standards
- Format with
magex format:fix. - Lint with
magex lintand vet withmagex vet. - Run
magex testbefore committing. - Follow Go naming and commenting conventions described in AGENTS.md.
Commit Messages
- Use the format
<type>(<scope>): <imperative short description>. - Types include
feat,fix,docs,test,refactor,chore,build,ci.
Pull Requests
- Title format:
[Subsystem] Imperative and concise summary of change. - Description must include the sections:
- What Changed
- Why It Was Necessary
- Testing Performed
- Impact / Risk
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 · 23 lines · 217 tokens per session scan A 5263be9ce4eb
cursorrules is a cursor rule published in the GitHub repository bsv-blockchain/spv-wallet-go-client (23 stars, last pushed 6d ago), licensed MIT. It adds 217 tokens to every session, about $0.0011 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-30.
Other cursor rules, from other repositories
cursorrules
All contributors must read .github/AGENTS.md for complete guidelines. If any rule here conflicts with that file, AGENTS.md takes precedence.
cursorrules
All contributors must read .github/AGENTS.md for complete guidelines. If any rule here conflicts with that file, AGENTS.md takes precedence.
cursorrules
All contributors must read .github/AGENTS.md for complete guidelines. If any rule here conflicts with that file, AGENTS.md takes precedence.
cursorrules
All contributors must read .github/AGENTS.md for complete guidelines. If any rule here conflicts with that file, AGENTS.md takes precedence.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.