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 yerdaulet-damir/vibe-coding-rules --skill new-feature-gogit clone --depth 1 https://github.com/yerdaulet-damir/vibe-coding-rulesWrote 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/yerdaulet-damir/vibe-coding-rules/new-feature-go)<a href="https://agentmods.dev/skills/yerdaulet-damir/vibe-coding-rules/new-feature-go"><img src="https://agentmods.dev/badge/skills/yerdaulet-damir/vibe-coding-rules/new-feature-go/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/yerdaulet-damir/vibe-coding-rules/new-feature-go"><img src="https://agentmods.dev/badge/skills/yerdaulet-damir/vibe-coding-rules/new-feature-go.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.00091 | $0.01591 |
| Opus 5.5 | $0.00036 | $0.00636 |
| Sonnet 5.5 | $0.00018 | $0.00318 |
| Haiku 4.5 | $0.00009 | $0.00159 |
Grade A, and why
new-feature-go 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-feature-go
Do not open any file for editing until all 6 steps are completed.
Step 1 — Define the surface
Write the surface in plain text first:
Feature name: credits
Public types: *Service (concrete), Repository (interface, lives next to Service)
Methods: Charge(ctx, userID, amount, idem) (string, error)
Confirm(ctx, holdID) error
Refund(ctx, holdID) error
Errors: ErrInsufficientFunds (sentinel), *ValidationError (typed)
Single-writer for: Repository.Hold — only Service.Charge calls it
If the public surface needs more than 5-6 methods, the package is doing too much — split it (Principle E2).
Step 2 — Pick the package location (Principle E1, E2)
| Scope | Location |
|---|---|
| Public library others import via go.mod | pkg/<name>/ |
| Private to this service | internal/<name>/ (default) |
| HTTP wiring / handlers | internal/server/ |
| Cross-cutting helpers (genuine ones) | internal/<purpose>/ (e.g. internal/httpclient) |
| Binary entry point | cmd/<binary>/main.go |
Forbidden package names: utils, helpers, common, shared, lib, misc. Pick a name that says what the package does.
Step 3 — Build bottom-up
1. Errors → internal/<name>/errors.go (sentinels + typed)
2. Repository iface → internal/<name>/repository.go (smallest set of methods)
3. Repository impl → internal/<name>/repository.go (MemoryRepo for tests, SQLRepo for prod)
4. Service struct → internal/<name>/service.go (concrete, accepts Repository)
5. Service tests → internal/<name>/service_test.go (table-driven, t.Run)
6. Handler → internal/server/handlers.go (defines tiny consumer interface)
7. Wiring → cmd/api/main.go (constructor injection)
Critical rules during build:
- Repository interface lives next to the Service that uses it — this is Go's hexagonal idiom (Principle E3).
- Service constructors return
*Service(concrete). Handlers accept the smallest interface they need (Principle F1). context.Contextis the first parameter of every I/O method (Principle F2).- Errors are returned, never
panic'd. Wrap with%w(Principle F3). - If integrating an external HTTP API, get its client from
httpclient.Get("<provider>")— never usehttp.DefaultClient(Principle F4).
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 · 168 lines · 91 tokens per session scan A 513f381752ec
new-feature-go is a skill published in the GitHub repository yerdaulet-damir/vibe-coding-rules (34 stars, last pushed 5mo ago), licensed MIT. It adds 91 tokens to every session and 1,591 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
skill-go-gin-api
Padrões DARE para APIs REST em Go + Gin (ou stdlib net/http) + sqlc + PostgreSQL. Handlers, services, repositories, middleware, validação com go-playground/validator, JWT, rate limit, swag (OpenAPI), testes com testify e httptest.
goframe-v2
GoFrame development skill. TRIGGER when writing/modifying Go files, implementing services, creating APIs, or database operations. DO NOT TRIGGER for frontend/shell scripts.
go
Use when writing, reviewing, testing, or shipping Go code and HTTP services: idioms, %w error wrapping, goroutine/context/errgroup concurrency, net/http 1.22 routing, log/slog, project layout, table-driven tests, Go hardening. NOT language-agnostic threat modeling (that is secure-coding), NOT Dockerfile/CI shipping…
go-backend-microservices
Go backend development best practices for microservices with clean architecture, observability, and production-ready patterns.
go-idioms
Go idioms and patterns: stdlib conventions, explicit error wrapping (%w), small interfaces, goroutines/channels concurrency, table-driven tests, and gofumpt formatting. Use when writing, refactoring, or reviewing Go services and packages.
agent-go-expert
Specialist subagent: Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.