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/atlas-hcl)<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/atlas-hcl"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/atlas-hcl/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/atlas-hcl"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/atlas-hcl.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.03142 |
| Opus 5 | $0.00000 | $0.01571 |
| Sonnet 5 | $0.00000 | $0.00628 |
| Haiku 4.5 | $0.00000 | $0.00314 |
Grade A, and why
atlas-hcl 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 10d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlas HCL File Rules
Overview
Rules for modifying HCL (HashiCorp Configuration Language) files (*.hcl) in go-crypto-wallet.
Supported DB Dialects
This project supports two database dialects: PostgreSQL and MySQL.
The DB_DIALECT variable (default: postgres) controls which dialect is targeted.
Applicable Directories
| Path | Description |
|---|---|
tools/atlas/schemas/postgres/ |
PostgreSQL schema definitions definitions (source of truth) |
tools/atlas/schemas/mysql/ |
MySQL schema definitions (source of truth) |
tools/atlas/atlas.hcl |
Atlas configuration (all environments) |
Schema Files
Each dialect has its own set of schema files:
| File | Description |
|---|---|
tools/atlas/schemas/{dialect}/watch.hcl |
Watch wallet schema (online) |
tools/atlas/schemas/{dialect}/keygen.hcl |
Keygen wallet schema (offline) |
tools/atlas/schemas/{dialect}/sign.hcl |
Sign wallet schema (offline) |
Where {dialect} is mysql or postgres.
Atlas Environments
Defined in tools/atlas/atlas.hcl:
| Environment | Dialect | Purpose |
|---|---|---|
local_postgres_watch |
PostgreSQL | Local watch DB |
local_postgres_keygen |
PostgreSQL | Local keygen DB |
local_postgres_sign |
PostgreSQL | Local sign DB |
admin_postgres_watch |
PostgreSQL | Admin (schema clean) |
admin_postgres_keygen |
PostgreSQL | Admin (schema clean) |
admin_postgres_sign |
PostgreSQL | Admin (schema clean) |
local_mysql_watch |
MySQL | Local watch DB |
local_mysql_keygen |
MySQL | Local keygen DB |
local_mysql_sign |
MySQL | Local sign DB |
admin_mysql_watch |
MySQL | Admin (schema clean) |
admin_mysql_keygen |
MySQL | Admin (schema clean) |
admin_mysql_sign |
MySQL | Admin (schema clean) |
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.
- 10d ago First seen · 362 lines · 0 tokens per session scan A 094115b18fff
atlas-hcl 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 3,142 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-01.
Other cursor rules, from other repositories
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
postgresql
PostgreSQL production rules. Safe migrations, parameterized queries, TIMESTAMPTZ, proper indexing strategy.
database-access
A database access pattern that separates browser reads from server-side reads and writes when using Supabase. Supabase is a hosted PostgreSQL service with rules that can restrict which users may access rows.
30-database-postgres
PostgreSQL and persistence rules.
neon-drizzle
Use this rules when integrating Neon (serverless Postgres) with Drizzle ORM.
neon-api-guidelines
Use these rules to understand how to interact with the Neon API, including authentication, rate limiting, and best practices.