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.
npx skills add hiromaily/go-crypto-wallet --skill mockerygit 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/skills/hiromaily/go-crypto-wallet/mockery)<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/mockery"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/mockery/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/skills/hiromaily/go-crypto-wallet/mockery"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/mockery.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.00063 | $0.01500 |
| Opus 5.5 | $0.00025 | $0.00600 |
| Sonnet 5.5 | $0.00013 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
mockery 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 1mo 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mockery Mock Generation Workflow
When to Activate This Skill
- A new interface is added to
internal/application/ports/ - A test file contains a manually-written mock/stub for a ports interface
- A developer asks to add mock coverage for an existing ports interface
- A test needs to replace
On(...).Return(...)setup on a hand-rolled struct with generated mock expectations
Placement Convention
Mocks live in the infrastructure layer, beside the concrete implementations:
Interface package (application/ports/) |
Mock output directory (infrastructure/) |
|---|---|
ports/api/btc/ |
infrastructure/api/btc/mocks/ |
ports/api/eth/ |
infrastructure/api/eth/mocks/ |
ports/api/xrp/ |
infrastructure/api/xrp/mocks/ |
ports/file/ |
infrastructure/storage/file/transaction/mocks/ |
ports/repository/cold/ |
infrastructure/repository/cold/mocks/ |
ports/repository/watch/ |
infrastructure/repository/watch/mocks/ |
Pattern: ports/<layer>/<pkg>/ → infrastructure/<layer>/<pkg>/mocks/
Step-by-Step Workflow
- Locate the interface — find the Go file in
internal/application/ports/that defines the interface. - Determine the target directory — use the placement convention table above to identify the
dirvalue. - Add or update
.mockery.yaml— append the interface name under its package entry (or add a new package entry if none exists). See the template below. - Run
make mockery— regenerates all mocks in one pass. Never create or edit mock files manually. - Verify — run
make go-lintandmake check-buildto confirm the generated code compiles cleanly. - Update tests — replace any manual stub usage with
NewMock*(t)+.EXPECT()builder calls.
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.
- 1mo ago First seen · 150 lines · 63 tokens per session scan A 4090b5f39cf8
mockery is a skill published in the GitHub repository hiromaily/go-crypto-wallet (128 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 1,500 once invoked, about $0.0003 per session on Opus 5.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-01.
Other skills, from other repositories
foundry-testing
Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working in tests/ or script/.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
verification-protocol
How to prove a hypothesis is TRUE or FALSE using Move unit tests.
blockchain-testing
Use this skill when asked about testing smart contracts, Foundry tests, Hardhat tests, fuzz testing, invariant testing, property-based testing, formal verification, audit preparation, integration testing for dApps, and blockchain testing patterns. Covers Foundry cheatcodes, Echidna fuzzing, Certora verification…
pqc-scan
Inventory the cryptography in a codebase that a quantum computer would break, and report what the scan could not read. Use when asked about post-quantum readiness, cryptographic inventory, a CBOM, or which algorithms a project signs with.
generate-tests
Creates comprehensive test suites for Move contracts with 100% coverage requirement. Triggers on: 'generate tests', 'create tests', 'write test suite', 'test this contract', 'how to test', 'add test coverage', 'write unit tests'.