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-db-cachegit 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-db-cache)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/go-db-cache"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-db-cache/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-db-cache"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-db-cache.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.00474 |
| Opus 5 | $0.00016 | $0.00237 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
go-db-cache 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 DB Cache
Every read and write is an access path: transaction boundary, tenant identity, query shape, and any cache's authority, freshness, invalidation, and fallback.
caller intent -> transaction -> query -> cache contract -> fallback -> observability -> proof
Trace the changed caller intent through its terminal result, including tenant identity, commit outcome, and resource lifetime. What must be atomically true together defines the transaction. A cache needs measured value, tenant-scoped keys, a freshness bound, an invalidation owner, and bounded origin fallback.
When comparing multiple affected access paths or handing off a Decision or
Review, record
AccessPath{caller, transaction, query, tenant, cache_authority, freshness, invalidation, fallback, commit_outcome, resource_lifetime, proof} for each path.
A single local path needs a grounded disposition and matching proof. For a
delegated Decision or Review, load the
shared specialist contract.
For a Decision, load transaction and commit outcome when deciding atomicity, safe retry, or an unknown commit. Reject a cache without measured need. For Review, load PostgreSQL access review when the query seam, rows, errors, or deadline changes. Complete when every access path has one atomicity and commit-outcome disposition and no cache can become an unnamed authority.
This template ships internal/infra/postgres and no data-cache client. A
distributed cache therefore adds a dependency and operational surface;
internal/health and internal/infra/oidcjwt are the in-process precedents.
Use cache engineering when cache semantics themselves are open and PostgreSQL performance for a measured database bottleneck.
What ships with it
2 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 · +5 lines c80f010c599c
- 10d ago First seen · 39 lines · 32 tokens per session scan A e2049a675cac
go-db-cache is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 474 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
golang-samber-hot
In-memory caching in Golang using samber/hot — eviction algorithms (LRU, LFU, TinyLFU, W-TinyLFU, S3FIFO, ARC, TwoQueue, SIEVE, FIFO), TTL, cache loaders, sharding, stale-while-revalidate, missing key caching, and Prometheus metrics. Apply when using or adopting samber/hot, when the codebase imports…
sq
Guides use of the sq CLI to query SQL databases and tabular files with SLQ (sq's jq-like query language) or native SQL, manage sources, choose output formats, and run inspect, diff, and table commands. Use when the user mentions sq, SLQ, wrangling CSV/Excel/JSON/DB data, cross-source joins, or command-line data…
using-redis-token-buckets
Use when adding a bucket-like rate limit backed by Redis: a per-caller budget with burst capacity and continuous refill, a refund path for requests that did no work, or a limit whose Retry-After must be a real wait rather than a window edge. posthog/tokenbucket.py provides an atomic Lua token bucket (consume, refund…
using-redis-token-buckets
Use when adding a bucket-like rate limit backed by Redis: a per-caller budget with burst capacity and continuous refill, a refund path for requests that did no work, or a limit whose Retry-After must be a real wait rather than a window edge. posthog/tokenbucket.py provides an atomic Lua token bucket (consume, refund…
spring-data-redis
Use when implementing caching, session storage, rate limiting, or any Redis integration. Covers cache-aside pattern, key naming, TTL strategy, and serialization config.
background-job-orchestrator
Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ"…