caching skillA
caching is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Decide what to cache, at which layer, for how long, and how it gets invalidated — before any cache is added. Use when someone proposes caching to make a read path faster, when stale or cross-user data is suspected, when adding a TTL or a Redis/CDN layer, or when reviewing a change that introduces one. Not for fixing a slow query or an N+1 (do that first — a cache over a bad query hides it), and not for HTTP header tuning with no server-side store..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Caching A cache is a second copy of the truth that is allowed to be wrong. Adding one trades a latency problem for a correctness problem, and the correctness problem arrives later, in production, as "why is this user seeing yesterday's number". Never add a cache before you can say, in one sentence each: what is cached, keyed by what, for how long, and what makes it wrong. ## When this fires A read path is slow and caching is being proposed; a cache already exists and data is stale or leaking across users; a review touches a TTL, a memoize decorator, a Redis client, or a CDN rule. It does not fire for a write path, or for a slow query nobody has profiled yet. ## Procedure 1. **Measure the uncached path first.** Get a real number — p50 and p95, and how often it is called. Without it you cannot tell afterwards whether the cache helped, and you have no basis for the TTL. A cache added on a hunch is a guess with extra failure modes. 2. **Try to make the cache unnecessary.** A missing index, an N+1, a payload fetching columns nobody reads, or a call made in a loop are all cheaper to fix than to cache, and the fix has …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/caching@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/caching@sha256:b755ccf8cd860eb7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ax7evthwbwja2yu5)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8730 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ax7evthwbwja2yu5 GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/caching GET https://markdownregistry.com/api/v1/blob/b755ccf8cd860eb7afabd4c6fa3cf9e7447474611a662efc516b7be816b8d39c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher