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.
git clone --depth 1 https://github.com/hiromaily/go-crypto-walletWrote 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/hiromaily/go-crypto-wallet/general)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/general"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/general.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.00430 | $0.00430 |
| Opus 5 | $0.00215 | $0.00215 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
general 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 4d 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
Claude Rules - General
Overview
General rules for Claude Code when working on go-crypto-wallet.
Behavior Guidelines
- Follow @AGENTS.md for behavior guidelines
- Refer to @docs/guidelines/ for detailed conventions
- Read @ARCHITECTURE.md for system design
Code Quality
Refer to @docs/guidelines/coding-conventions.md
Key rules:
- Follow Clean Architecture layer separation
- Domain layer has ZERO infrastructure dependencies
- Follow language-specific conventions (see Skills below)
- Run file-type-appropriate verification commands before committing (see table below;
*.mdrequires none)
Testing
Refer to @docs/guidelines/testing.md
Workflow
Refer to @docs/guidelines/workflow.md
Key rules:
- Check current branch FIRST before starting any task (never work on
main) - Create feature branches for changes
- Follow conventional commit messages
- Run file-type-appropriate verification commands before committing (see table below;
*.mdrequires none)
Language-Specific Skills
Use appropriate skills based on the file type:
| File Type | Skill | Verification |
|---|---|---|
Go (*.go) |
go-development |
make go-lint, make check-build |
TypeScript (*.ts) |
typescript-development |
npm run lint, npm run build |
Shell (*.sh) |
shell-scripts |
make shfmt |
Solidity (*.sol) |
solidity-development |
(see skill) |
| SQL/HCL | db-migration |
make atlas-fmt, make atlas-lint |
| Makefile | makefile-update |
make mk-lint |
Markdown (*.md) |
docs-update |
(none required) |
Auto-Generated Files
DO NOT EDIT files containing DO NOT EDIT comments.
See language-specific skills for details on auto-generated file locations.
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.
- 4d ago First seen · 62 lines · 430 tokens per session scan A 3f5a8e90481b
general is a cursor rule published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 430 tokens to every session, about $0.0022 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-03.
Other cursor rules, from other repositories
development_workflow
Spamoor Development Workflow and Best Practices.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
commit
Cursor rule "commit" from RyabininAleck/cursor_rules_golang, covering identity and purpose, workflow, guidelines, commit message format and output examples.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
code_standards
Spamoor Code Standards and Conventions.
commands
Common workspace commands for skia-rs development.