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-delivery-platformgit 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-delivery-platform)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/go-delivery-platform"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-delivery-platform/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-delivery-platform"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-delivery-platform.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.00032 | $0.00412 |
| Opus 5.5 | $0.00013 | $0.00165 |
| Sonnet 5.5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
go-delivery-platform 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.
What it actually says
Go Delivery Platform
Delivery trust is a chain of gates with named artifacts, pass conditions, exceptions, and recovery consequences.
accepted policy -> gate inventory -> artifact and command -> pass condition -> exception owner -> rollout and recovery -> proof
Inventory the gates required by the accepted delivery policy. The presence of a status, parity check, container, migration, or available control does not create an additional acceptance gate. For a required gate, a waiver has an owner and expiry; drift between declared and actual controls is a finding.
For a delegated Decision or Review, or when the active artifact requires its
result interface, load the
shared specialist contract.
When meaningful ordering, comparison, exhaustive accounting, or a required
decision/review handoff needs structured representation, trace accepted delivery policy to terminal rollout or rollback in
DeliveryGate{control, artifact, command, pass_condition, exception_owner, expiry, rollout, recovery, proof} for every required status, parity check,
provenance rule, container, migration, or runtime control.
Otherwise, a single local control may retain its grounded gate judgment and
proof, including its exception and recovery disposition.
Choose The Branch
- Decision — load one matching decision reference and disposition every gate, forced consequence, proof, and exception owner.
- Review — load one matching review reference and account for every gate; a waived required gate remains a finding.
Complete only when every required gate has a current artifact, fail-closed pass condition, exception disposition, and recovery consequence. A green job that did not compare or exercise its intended surface is not a passing gate.
What ships with it
5 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.
- 1mo ago Changed · +4 lines · -3 tokens per session c67cb8439eaa
- 1mo ago Changed · +2 lines 073bfa50e7b3
- 1mo ago First seen · 36 lines · 35 tokens per session scan A e6a5c8c35123
go-delivery-platform is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 412 once invoked, about $0.0001 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
go-deploy
Build and deploy Go applications — version detection, static binaries, CGO, workspaces, and Dockerfile patterns. Use when deploying a Go project, or when go.mod is detected.
gh-actionlint
Validate GitHub Actions workflow YAML with actionlint when editing files under .github/workflows/, checking CI workflow syntax, diagnosing GitHub Actions expression or schema errors, or when the user asks to lint/check Actions workflows. Prefer bunx github-actionlint when bun is available and fall back to npx --yes…
gh-ci-watch
Watch GitHub PR checks with gh, poll until green/failure/timeout, fetch failed GitHub Actions logs, save logs locally, summarize actionable CI failures, and apply trivial local fixes when safe. Use when the user asks to watch PR checks, wait for CI, inspect failed actions, fix obvious CI failures, or summarize gh pr…
golang-continuous-integration
CI/CD pipeline configuration using GitHub Actions for Golang projects — testing, linting, SAST, security scanning, code coverage, Dependabot, Renovate, GoReleaser, code review automation, and release pipelines. Use when setting up or improving Go project CI, configuring GitHub Actions workflows, adding linters or…
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…