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/security)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/security"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/security/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/hiromaily/go-crypto-wallet/security"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/security.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.00263 | $0.00263 |
| Opus 5 | $0.00131 | $0.00131 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
security 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 7d 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 - Security
Overview
Security rules for Claude Code when working on go-crypto-wallet. Security is paramount - this project handles private keys and cryptocurrency transactions.
Detailed Rules
Refer to @docs/guidelines/security.md for full security requirements.
Quick Reference
Critical Rules
- NEVER log private keys or sensitive information
- NEVER commit secrets or credentials
- Always validate inputs at system boundaries
- Consider offline wallet implications for keygen/sign operations
- Security-related changes must be reviewed
Security-Critical Areas
internal/infrastructure/wallet/key/- Key generationinternal/domain/key/- Key value objects- Any code handling private keys, seeds, or passwords
Wallet Architecture
| Wallet | Environment | Security Level |
|---|---|---|
| Watch | Online | Public keys only |
| Keygen | Offline | Generates private keys |
| Sign | Offline | Signs transactions |
Verification
Before committing security-related changes:
make go-check-vuln
make go-lint
make go-test
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.
- 7d ago First seen · 50 lines · 263 tokens per session scan A 411b64b2b577
security is a cursor rule published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 263 tokens to every session, about $0.0013 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.