ardanlabs/service is a Go starter kit for building scalable web services designed to run in Kubernetes. It provides an organized starting structure based on domain-driven and data-oriented architecture, Go practices, and a small dependency set. The catalogue skills and instruction help coding agents work with services built from this starter kit.
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 ardanlabs/service --skill business-layer-extensionsgit clone --depth 1 https://github.com/ardanlabs/serviceWrote 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/ardanlabs/service/business-layer-extensions)<a href="https://agentmods.dev/skills/ardanlabs/service/business-layer-extensions"><img src="https://agentmods.dev/badge/skills/ardanlabs/service/business-layer-extensions/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/ardanlabs/service/business-layer-extensions"><img src="https://agentmods.dev/badge/skills/ardanlabs/service/business-layer-extensions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.01290 |
| Opus 5 | $0.00029 | $0.00645 |
| Sonnet 5 | $0.00012 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
business-layer-extensions 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 9d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Layer Extensions
The business layer layers cross-cutting concerns onto core domain logic with a
decorator pattern: each extension wraps an ExtBusiness and delegates to it.
Wrap, never modify the core Business. An extension that adds tracing to one
method must still implement every other method as a plain pass-through.
It comes in three coordinated pieces: the seam on the bus (Piece 1), the extension package itself (Piece 2), and the wiring that registers it (Piece 3).
Checklist
- Seam exists? Confirm the target
<x>bus.gohasExtBusiness,Extension, and the reverse-apply loop inNewBusiness. If not, add them (piece 1). - Create
extensions/<x><concern>/<x><concern>.go(piece 2). - Implement EVERY
ExtBusinessmethod — wrap the relevant ones, pass the rest straight through toext.bus. Missing one fails to satisfy the interface and won't compile. - Wire into
api/services/*/main.goin the right order (piece 3).
Piece 1 — the seam (in <x>bus/<x>bus.go)
// ExtBusiness lists every public method an extension can wrap.
type ExtBusiness interface {
Create(ctx context.Context, input CreateInput) (Model, error)
// ... every other public business method
}
// Extension wraps a new layer of business logic around the existing logic.
type Extension func(ExtBusiness) ExtBusiness
func NewBusiness(log *logger.Logger, delegate *delegate.Delegate, storer Storer, extensions ...Extension) ExtBusiness {
b := ExtBusiness(&Business{ /* ... */ })
for i := len(extensions) - 1; i >= 0; i-- { // reverse: first-listed = outermost
if ext := extensions[i]; ext != nil {
b = ext(b)
}
}
return b
}
Piece 2 — the extension (extensions/<x><concern>/<x><concern>.go)
Package name is <x><concern> (e.g. widgetotel, widgetlog). Struct holds the
wrapped bus plus any deps; NewExtension returns the closure.
// Package widgetotel provides an extension for WidgetBus to add OTEL related
// code on top of it without changing the existing logic.
package widgetotel
type Extension struct {
bus widgetbus.ExtBusiness
}
func NewExtension() widgetbus.Extension {
return func(bus widgetbus.ExtBusiness) widgetbus.ExtBusiness {
return &Extension{bus: bus}
}
}
// Wrapped method — adds the concern, then delegates.
func (ext *Extension) Create(ctx context.Context, input widgetbus.CreateWidgetInput) (widgetbus.Widget, error) {
ctx, span := otel.AddSpan(ctx, "business.widgetbus.create")
defer span.End()
w, err := ext.bus.Create(ctx, input)
if err != nil {
span.RecordError(err)
span.SetStatus(codes.Error, err.Error())
return w, err
}
span.SetStatus(codes.Ok, "")
return w, nil
}
// Pass-through method — NOT relevant to this concern, but REQUIRED for the interface.
func (ext *Extension) Delete(ctx context.Context, w widgetbus.Widget) error {
return ext.bus.Delete(ctx, w)
}
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.
- 9d ago First seen · 148 lines · 58 tokens per session scan A 597be9cbb405
business-layer-extensions is a skill published in the GitHub repository ardanlabs/service (4,110 stars, last pushed 10d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,290 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-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.