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 egravert/egravert-marketplace --skill go-hexagonalgit clone --depth 1 https://github.com/egravert/egravert-marketplaceWrote 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/egravert/egravert-marketplace/go-hexagonal)<a href="https://agentmods.dev/skills/egravert/egravert-marketplace/go-hexagonal"><img src="https://agentmods.dev/badge/skills/egravert/egravert-marketplace/go-hexagonal/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/egravert/egravert-marketplace/go-hexagonal"><img src="https://agentmods.dev/badge/skills/egravert/egravert-marketplace/go-hexagonal.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.00070 | $0.04189 |
| Opus 5 | $0.00035 | $0.02094 |
| Sonnet 5 | $0.00014 | $0.00838 |
| Haiku 4.5 | $0.00007 | $0.00419 |
Grade A, and why
Go Layered Architecture 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Layered Architecture
Opinionated, pragmatic guide for building Go applications using a layered architecture inspired by hexagonal (ports and adapters) principles. This is not a pure hexagonal implementation — it intentionally flattens the ports-and-adapters model into a straightforward layered structure where dependencies flow inward toward the domain core. The goal is clarity and navigability over architectural purity: each layer has clear responsibilities and boundaries without the extra indirection that strict hexagonal architecture introduces.
Dependency Flow
Interface (CLI/TUI/Web) → Service → Domain ← Storage
↑
Adapters (external APIs)
- Domain defines interfaces (ports). Storage and external client adapters implement them.
- Services depend on domain interfaces, never on concrete storage or external client packages.
- Interface layers depend on services, never on storage or domain internals.
Directory Structure
project/
├── cmd/
│ ├── cli/ # urfave/cli entry point
│ ├── tui/ # bubbletea entry point
│ └── web/ # chi router entry point
├── internal/
│ ├── domain/ # Entities, value objects, repository + client interfaces
│ ├── service/ # Business logic, validation, orchestration
│ ├── storage/ # Repository implementations (wraps sqlc)
│ │ └── db/ # sqlc-generated code (do not edit)
│ ├── <client>/ # External API adapters (e.g., bgg/, stripe/)
│ ├── cli/ # CLI command handlers
│ ├── tui/ # Bubbletea models and views
│ └── web/ # Chi handlers, middleware, templates
├── db/
│ ├── migrations/ # goose SQL migrations
│ └── queries/ # sqlc SQL query files
├── sqlc.yml
└── go.mod
Domain Layer
The domain layer is the innermost ring. It has zero external dependencies — no framework imports, no struct tags, no database concerns. Include a doc.go with a glossary of key business concepts so that new contributors (human or agent) can understand the domain language.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 450 lines · 70 tokens per session scan A e991ddd078f7
Go Layered Architecture is a skill published in the GitHub repository egravert/egravert-marketplace (4 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 4,189 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.
golang-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or…
golang-pro
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming…
golang-swagger
Golang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example…
layered-architecture-types
Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/, business/domain/, or .../stores/db.
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…