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 go-developmentgit 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/go-development)<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/go-development"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/go-development/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/go-development"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/go-development.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.00029 | $0.00331 |
| Opus 5.5 | $0.00012 | $0.00132 |
| Sonnet 5.5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
go-development 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.
What it actually says
Go Development Workflow
Workflow for Go code changes in this repository.
Prerequisites
- Use
git-workflowSkill for branch management, commit conventions, and PR creation. - Refer to
.claude/rules/go.mdfor detailed verification commands and coding rules (SSOT).
Applicable Directories
| Directory | Description |
|---|---|
internal/ |
Core application code (Clean Architecture) |
pkg/ |
Reusable shared packages |
cmd/ |
Application entry points |
Workflow
1. Make Changes
Edit Go files following the rules in .claude/rules/go.md.
2. Verify (from rules/go.md)
make go-lint && make tidy && make check-build && make go-test
3. Self-Review Checklist
- Domain layer has ZERO infrastructure dependencies
- Error handling uses
fmt.Errorf("context: %w", err) - No private keys or sensitive data logged
- Auto-generated files not edited
Database Changes
If modifying database schema, use db-migration skill.
Related
.claude/rules/go.md- Go rules (SSOT)git-workflow- Branch, commit, PR workflowdb-migration- Database schema workflow
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 · 51 lines · 29 tokens per session scan A d2aacafbbba0
go-development is a skill published in the GitHub repository hiromaily/go-crypto-wallet (128 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 331 once invoked, about $0.0001 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
setup
Wire Ginkgo into a Go package — install the ginkgo CLI and Ginkgo+Gomega, ginkgo bootstrap to generate the suitetest.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs), the package xxxtest convention, dot-import alternatives (aliased import, dsl/ subpackages, --nodot), ginkgo generate, and testing.T interop via…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…
eng-test-conventions
Go test-shape discipline for Compozy. Use when writing or editing test.go under cmd or internal after test placement is justified. Do not use for non-Go tests, fixture-only changes, or as a replacement for eng-consolidate-test-suites.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
assertions
Write correct synchronous Gomega assertions — Expect/Ω notation, the To/NotTo/ToNot/Should/ShouldNot equivalences, the multi-return error idiom, Succeed vs HaveOccurred, the .Error() chaining form, annotating assertions (format-string and func()string), tuning failure output via the format subpackage…
gbytes
Testing streaming io buffers with gbytes — gbytes.NewBuffer() (an io.Writer also returned by gexec sessions), the Say(regexp) matcher that forward-scans from a moving read cursor, the canonical Eventually(buffer).Should(Say(...)) streaming pattern, sequential cursor-advancing Say calls, Contents()…