interface-adapters-layer

interface-adapters-layer is a cursor rule for Cursor from hiromaily/go-crypto-wallet. It costs 0 tokens per session (769 once invoked), scanned A, original, MIT.

Rules for the layer that connects outside interfaces, such as command-line commands and HTTP handlers, to application operations. It defines how these adapters are organized and how they may depend on the rest of the application.

In plain words
What is it for?
Use it when adding CLI commands, HTTP handlers, middleware, or wallet adapters for Bitcoin, Ethereum, or XRP. It guides their folder structure and dependency direction.
Why use it?
It keeps command-line and web-specific code separate from business logic. This makes the same application operations usable through different interfaces without mixing concerns.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding CLI commands, HTTP handlers, middleware, or wallet adapters for Bitcoin, Ethereum, or XRP. It guides their folder structure and dependency direction.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/hiromaily/go-crypto-wallet/interface-adapters-layer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet

Made for: Cursor.

Wrote 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.

agentmods badge for interface-adapters-layer

README.md
[![agentmods](https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/interface-adapters-layer/github.svg)](https://agentmods.dev/rules/hiromaily/go-crypto-wallet/interface-adapters-layer)
Your own site
<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/interface-adapters-layer"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/interface-adapters-layer/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.

agentmods 80×15 button for interface-adapters-layer

Your own site · 80×15
<a href="https://agentmods.dev/rules/hiromaily/go-crypto-wallet/interface-adapters-layer"><img src="https://agentmods.dev/badge/rules/hiromaily/go-crypto-wallet/interface-adapters-layer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00769
Opus 5 $0.00000 $0.00385
Sonnet 5 $0.00000 $0.00154
Haiku 4.5 $0.00000 $0.00077

Measured 7d ago against content hash 0c002e7d9069, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

interface-adapters-layer 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.

.cursor/rules/internal/interface-adapters-layer.mdc · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Interface Adapters Layer Rules

Overview

Rules for working with the Interface Adapters layer (internal/interface-adapters/). This layer adapts external interfaces (CLI, HTTP) to application use cases.

Structure

internal/interface-adapters/
├── cli/            # CLI command adapters
│   ├── app/        # App initialization, flags, validation
│   ├── keygen/     # Key generation commands
│   │   ├── api/    # API commands (btc, eth)
│   │   ├── create/ # Creation commands
│   │   ├── export/ # Export commands
│   │   └── imports/# Import commands
│   ├── sign/       # Sign wallet commands
│   └── watch/      # Watch wallet commands
│       ├── api/    # API commands (btc, eth, xrp)
│       ├── create/ # Creation commands
│       ├── imports/# Import commands
│       ├── monitor/# Monitor commands
│       └── send/   # Send commands
├── http/           # HTTP handlers and middleware
└── wallet/         # Wallet adapters
    ├── btc/        # Bitcoin (keygen, sign, watch)
    ├── eth/        # Ethereum (keygen, sign, watch)
    └── xrp/        # XRP (keygen, sign, watch)

Key Principle

Interface Adapters depend ONLY on the Application layer.

  • Call use cases from application/usecase/
  • Convert external input (CLI args, HTTP requests) to use case input
  • Convert use case output to external output (CLI output, HTTP responses)

Command Pattern

type CreateCommand struct {
    useCase usecase.CreateUseCase  // Application layer use case
}

func (c *CreateCommand) Run(args []string) error {
    // 1. Convert CLI args to use case input
    input := usecase.CreateInput{
        Param1: args[0],
    }

    // 2. Call use case
    output, err := c.useCase.Execute(context.Background(), input)
    if err != nil {
        return fmt.Errorf("failed to create: %w", err)
    }

    // 3. Format output for CLI
    fmt.Printf("Created: %s\n", output.Result)
    return nil
}

Allowed/Forbidden

Action Allowed
Import from application/usecase/ Yes
Import from application/dto/ Yes
Import from domain/ No
Import from infrastructure/ No
Contain business logic No (delegate to use cases)
Call infrastructure directly No (use use cases)

Read the full file on GitHub · 111 lines

Changes

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.

  1. 7d ago First seen · 111 lines · 0 tokens per session scan A 0c002e7d9069

Subscribe to this mod's changes

interface-adapters-layer 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 769 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.