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 daibang123a/golang-agent-skills --skill api-design-guidelinesgit clone --depth 1 https://github.com/daibang123a/golang-agent-skillsWrote 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/daibang123a/golang-agent-skills/api-design-guidelines)<a href="https://agentmods.dev/skills/daibang123a/golang-agent-skills/api-design-guidelines"><img src="https://agentmods.dev/badge/skills/daibang123a/golang-agent-skills/api-design-guidelines/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/daibang123a/golang-agent-skills/api-design-guidelines"><img src="https://agentmods.dev/badge/skills/daibang123a/golang-agent-skills/api-design-guidelines.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.00080 | $0.02280 |
| Opus 5 | $0.00040 | $0.01140 |
| Sonnet 5 | $0.00016 | $0.00456 |
| Haiku 4.5 | $0.00008 | $0.00228 |
Grade A, and why
api-design-guidelines 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 12d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go API Design Guidelines
Review and build Go HTTP APIs following REST best practices, security hardening, and production-grade patterns. 80+ rules across 9 categories.
How It Works
- Agent examines HTTP handler code, middleware, routing, and configuration
- Agent applies rules by category in priority order
- Agent suggests specific fixes with idiomatic Go code examples
- Agent references supporting docs for deep-dive topics
Rules
1. Routing & Middleware (Critical)
| # | Rule | Description |
|---|---|---|
| R1 | Use Go 1.22+ ServeMux or a minimal router | http.ServeMux now supports GET /users/{id}. Prefer stdlib for simple APIs. Use chi or gorilla/mux only when pattern matching is insufficient. |
| R2 | Apply middleware in correct order | Order matters: Recovery → Logging → CORS → Auth → Rate Limit → Handler. |
| R3 | Use middleware for cross-cutting concerns | Authentication, logging, tracing, rate limiting, and CORS belong in middleware, not in handlers. |
| R4 | Group routes by resource | /api/v1/users, /api/v1/users/{id}, /api/v1/users/{id}/orders. |
| R5 | Use http.Handler interface | All middleware should accept and return http.Handler for composability. |
| R6 | Set timeouts on http.Server | Always set ReadTimeout, WriteTimeout, IdleTimeout. Never use http.ListenAndServe with default server. |
// GOOD: Production server with timeouts
srv := &http.Server{
Addr: ":8080",
Handler: mux,
ReadTimeout: 5 * time.Second,
WriteTimeout: 10 * time.Second,
IdleTimeout: 120 * time.Second,
}
2. Request Handling (Critical)
| # | Rule | Description |
|---|---|---|
| Q1 | Validate all input | Never trust client input. Validate struct fields, query params, path params. |
| Q2 | Limit request body size | Use http.MaxBytesReader to prevent memory exhaustion from large payloads. |
| Q3 | Use json.Decoder, not io.ReadAll + json.Unmarshal | Decoder streams and can enforce DisallowUnknownFields(). |
| Q4 | Return early on validation errors | Don't process a request if input is invalid. Return 400 immediately. |
| Q5 | Bind path params safely | Always validate and convert path parameters. Never use raw strings in queries. |
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.
- 12d ago First seen · 197 lines · 80 tokens per session scan A aed2a653d347
api-design-guidelines is a skill published in the GitHub repository daibang123a/golang-agent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 80 tokens to every session and 2,280 once invoked, about $0.0004 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
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
api-reviewer
A review of an API contract, the agreed description of how software systems exchange requests, responses, events, or files.