Borrowing it
Nothing to install: this file belongs to hiromaily/go-crypto-wallet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hiromaily/go-crypto-wallet/main/AGENTS.mdgit 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/instructions/hiromaily/go-crypto-wallet/agents-md)<a href="https://agentmods.dev/instructions/hiromaily/go-crypto-wallet/agents-md"><img src="https://agentmods.dev/badge/instructions/hiromaily/go-crypto-wallet/agents-md/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/instructions/hiromaily/go-crypto-wallet/agents-md"><img src="https://agentmods.dev/badge/instructions/hiromaily/go-crypto-wallet/agents-md.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.01403 | $0.01403 |
| Opus 5 | $0.00701 | $0.00701 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
go-crypto-wallet AGENTS.md 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- go-crypto-wallet CLAUDE.md — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines for go-crypto-wallet
This document defines the behavior and values for AI agents working on this project. For detailed documentation, see llms.txt and ARCHITECTURE.md.
Project Identity
- Type: Multi-signature cryptocurrency wallet (BTC, BCH, ETH, XRP, ERC-20)
- Security Model: Offline cold wallets (keygen, sign) + Online watch wallet
- Architecture: Clean Architecture with strict layer separation
- Status: Under refactoring based on Clean Code principles
Core Values (Priority Order)
- Security First - Private key protection is non-negotiable
- Clean Architecture - Domain layer has ZERO infrastructure dependencies
- Single Source of Truth (SSOT) - One authoritative location for each piece of information
- Incremental Changes - No breaking changes without rollback plan
- Code Quality - Follow language-specific linting and testing standards
Expected Behavior
Always Do
- Check current branch before starting any task (see
git-workflowskill) - Read relevant documentation before making changes
- Run verification commands after code changes
- Wrap errors with context using
fmt.Errorf("context: %w", err) - Consider impact on offline wallet operations
Never Do
- ❌ Log private keys or sensitive information
- ❌ Edit files marked
DO NOT EDIT(auto-generated) - ❌ Push directly to
mainbranch - ❌ Run
git mergeorgh pr merge - ❌ Run
protocorbufcommands directly (always use Makefile targets likemake proto,make proto-ts)
Ask Before
- Making security-related changes
- Breaking changes to public APIs
- Changes affecting multiple layers
SSOT Structure
When modifying rules, skills, or documentation, always edit the SSOT location.
AI Agent Configuration
| Category | SSOT Location | Other Locations |
|---|---|---|
| Rules | .claude/rules/*.md |
.cursor/rules/*.mdc (auto-generated) |
| Skills | .claude/skills/*/SKILL.md |
.cursor/skills/ (symlink) |
| Commands | .claude/commands/ |
.cursor/commands/ (reference only) |
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 · 133 lines · 1,403 tokens per session scan A fb75e67f4dde
go-crypto-wallet AGENTS.md is an instructions file published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 1,403 tokens to every session, about $0.0070 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.