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/yaml)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/yaml"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/yaml/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/yaml"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/yaml.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.00000 | $0.00625 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
yaml 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YAML File Rules
Overview
Rules for modifying YAML files (*.yaml, *.yml) in go-crypto-wallet.
Applicable Directories
| Directory | Description |
|---|---|
config/ |
Application configuration files |
.github/workflows/ |
GitHub Actions workflows |
.devcontainer/ |
Dev container configuration |
Root (*.yaml) |
Docker Compose, tool configurations |
Verification Commands
| Command | Purpose | Required |
|---|---|---|
make yaml-lint |
Lint YAML files | Recommended |
Target Directories for yaml-lint
The yaml-lint command checks:
.github/workflows/.devcontainer/config/
Configuration File Types
Application Config (config/)
Wallet configuration files for BTC, BCH, ETH, XRP:
# Example: config/wallet/btc/watch.yaml
bitcoin:
network: testnet
host: "127.0.0.1:18332"
Docker Compose (compose*.yaml)
Service definitions:
| File | Description |
|---|---|
compose.yaml |
Base services (database, etc.) |
compose.btc.yaml |
Bitcoin services |
compose.bch.yaml |
Bitcoin Cash services |
compose.eth.yaml |
Ethereum services |
compose.xrp.yaml |
Ripple services |
GitHub Actions (.github/workflows/)
CI/CD workflow definitions.
Validation
Manual Validation
# Validate YAML syntax
python -c "import yaml; yaml.safe_load(open('file.yaml'))"
# Or using yq
yq eval '.' file.yaml > /dev/null
Docker Compose Validation
docker compose config
Best Practices
Formatting
- Use 2 spaces for indentation
- Use quotes for strings that could be misinterpreted
- Keep lines under 120 characters
Structure
# Good: Explicit quotes for version strings
version: "3.8"
# Good: Explicit quotes for port mappings
ports:
- "8080:80"
# Good: Anchors for repeated values
defaults: &defaults
restart: unless-stopped
services:
app:
<<: *defaults
Quick Checklist
- Valid YAML syntax
- Consistent indentation (2 spaces)
- Sensitive values use environment variables, not hardcoded
- Port mappings are quoted
- Comments explain non-obvious configurations
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 · 128 lines · 0 tokens per session scan A 3c0f6bc82a01
yaml is a cursor rule published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 625 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-09-03.
Other cursor rules, from other repositories
documentation
Documentation discovery index for Lineth monorepo.
architecture
../../.agents/rules/architecture.md.
design-system
../../.agents/rules/design-system.md.
env-vars
../../.agents/rules/env-vars.md.
tests-unit
../../.agents/rules/tests-unit.md.
typescript
../../.agents/rules/typescript.md.