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 agentmods add skills/dankosik/go-service-template-rest/cache-engineeringnpx skills add Dankosik/go-service-template-rest --skill cache-engineeringgit 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/cache-engineering)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/cache-engineering"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/cache-engineering.svg" alt="Measured on agentmods" 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.00028 | $0.00215 |
| Opus 5 | $0.00014 | $0.00108 |
| Sonnet 5 | $0.00006 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
cache-engineering 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 6d 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
Cache Engineering
Use only after the active phase identifies a cache-specific decision. Inherit its authority, artifact, review, proof, output, and completion contract; do not select design, diagnosis, implementation, review, or production-action mode.
Core invariant: a cache is a bounded copy with explicit authority, key scope, freshness, fill and invalidation ownership, degraded behavior, and a falsifier. Reject a cache whose measured value does not justify that complexity.
Load one branch:
- whether caching should exist -> value.md;
- value, key, freshness, or invalidation contract -> contract.md;
- concurrent fill, hot key, outage, or layer-specific behavior -> runtime.md;
- migration, rollout, or proof -> rollout-proof.md.
What ships with it
4 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.
- 6d ago First seen · 24 lines · 28 tokens per session scan A 6dba74d3ccac
cache-engineering is a skill published in the GitHub repository Dankosik/go-service-template-rest (6 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 215 once invoked, about $0.0001 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…
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…
db
Database schema and query conventions for ThunderID. Use when changing schema scripts, defining SQL queries, updating store constants, or reviewing deployment-scoped persistence rules.
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.
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…
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…