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 Dankosik/go-service-template-rest --skill go-implementation-ownershipgit clone --depth 1 https://github.com/Dankosik/go-service-template-restWrote 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/dankosik/go-service-template-rest/go-implementation-ownership)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/go-implementation-ownership"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-implementation-ownership/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/dankosik/go-service-template-rest/go-implementation-ownership"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-implementation-ownership.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.00035 | $0.00515 |
| Opus 5 | $0.00017 | $0.00258 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
go-implementation-ownership 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 3d 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 Implementation Ownership
Every piece of logic, wiring, and proof has one owner. Two plausible owners means placement is not decided.
responsibilities -> owner -> dependency direction -> generated/manual authority -> proof placement -> cleanup
For a delegated Decision or Review, or when the active artifact requires its
result interface, load the
shared specialist contract.
For every changed responsibility, build OwnerRecord{responsibility, canonical_source, package, file, dependency_direction, sequence_owner, existing_proof_location_if_known, competing_paths, cleanup} from accepted
behavior through callers, wiring, generated and manual sources, and cleanup.
Ownerless, duplicated, or competing production paths are findings. Implementation
chooses new test cases, files, and proving layers while writing code; their
absence does not block the ownership decision.
The nearest record wins: read package doc.go, README.md, and seam comments
before Repository Architecture, Project
Structure, and
Configuration Source Policy.
Gates prove only what they inspect; use .golangci.yml and scripts/ci/ to
subtract mechanical coverage rather than treating green as ownership evidence.
Cohesion: Group declarations that must be understood and changed together. Use package boundaries for dependency and API isolation, and files for navigable, cohesive behavior.
Caller view: Exercise each new or changed package boundary from a real caller's perspective; make inputs, results, errors, and lifecycle obligations understandable without inspecting implementation details.
Debug path: Walk a representative failure symptom through the proposed owners to the responsible rule, effect, and regression-test location. Reduce unrelated context needed to follow that path.
For a Decision, apply Project Structure's placement rules and record forced consequences for every responsibility. For Review, account for every affected owner and competing path. Complete only when implementation can proceed from a current, unambiguous map of production packages, files, sources, and dependency boundaries. This method establishes code ownership, not an approved test plan or proof level before Implementation.
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.
- 3d ago Changed · +2 lines 96a1cad10024
- 4d ago Changed · +3 lines 4f0ab3c736e9
- 6d ago Changed · +12 lines a5d478e61787
- 11d ago First seen · 35 lines · 35 tokens per session scan A c1bc0c94cb21
go-implementation-ownership is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 515 once invoked, about $0.0002 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
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
migrate-goldmark-app-v1-to-v2
Migrate your application from goldmark v1 to v2.
jwx-guide-v4
Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse/sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid the common footguns. For developers using jwx, not for developing the library itself.
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…