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-observabilitygit 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-observability)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/go-observability"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-observability/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-observability"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-observability.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.00044 | $0.00499 |
| Opus 5 | $0.00022 | $0.00249 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
go-observability 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 Observability
Telemetry is operator evidence: every signal answers a named operational question or is avoidable cost.
operator question -> signal -> SLI/SLO -> alert -> correlation -> cardinality, privacy, and cost -> proof
For a delegated Decision or Review, or when the active artifact requires its
result interface, load the
shared specialist contract.
Trace each changed signal from its operator question to the page or diagnostic
action it enables, using accepted outcomes, runtime paths, current telemetry,
dashboards, and alerts. For interacting signals, exhaustive coverage, or a
decision/review handoff, record
OperatorSignal{question, signal, SLI, alert, correlation, labels, privacy, cost, owner, proof}. A local field change can keep its purpose, privacy, cardinality,
and cost judgment in the code or existing artifact; it does not require a new
SLI or alert. Alert on user-visible symptoms; keep causes as correlated
diagnosis surfaces. Treat label cardinality
as a budget and every emitted field as a disclosure surface.
Load the selector for a new or widened metric label, instrument, resource attribute, cross-service correlation, log event, payload logging, readiness signal, or debug surface. Its reference carries the accepted policy and enforcing repository owner.
For a Decision, disposition every operator question and signal with privacy, cardinality, diagnostic, and cost bounds. For Review, account for every affected signal. A signal that cannot answer its named question or has no bounded labels and readers is not complete.
Use production diagnosis for cross-service localization, reliable messaging for producer, consumer, DLQ, redrive, and replay signals, and durable jobs for queue age, leases, checkpoints, and drain.
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.
- 3d ago Changed · +6 lines 2bfacb09338b
- 11d ago First seen · 39 lines · 44 tokens per session scan A da5ede5a69b4
go-observability is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 499 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
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.
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.
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…