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 elbwalker/walkerOS --skill walkeros-using-store-cachegit clone --depth 1 https://github.com/elbwalker/walkerOSWrote 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/elbwalker/walkeros/walkeros-using-store-cache)<a href="https://agentmods.dev/skills/elbwalker/walkeros/walkeros-using-store-cache"><img src="https://agentmods.dev/badge/skills/elbwalker/walkeros/walkeros-using-store-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/elbwalker/walkeros/walkeros-using-store-cache"><img src="https://agentmods.dev/badge/skills/elbwalker/walkeros/walkeros-using-store-cache.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.04234 |
| Opus 5.5 | $0.00022 | $0.01694 |
| Sonnet 5.5 | $0.00011 | $0.00847 |
| Haiku 4.5 | $0.00006 | $0.00423 |
Grade A, and why
walkeros-using-store-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using store-level cache
Overview
Flow.Store.cache wraps any store with a read-through, write-through cache
tier. Reads check the cache first, fall through to the backing on miss, and
populate every tier on the unwind. Writes go to the backing first, then to the
cache best-effort.
The wrapping is transparent: a transformer wired to $store.crm does not know
whether reads hit a memory cache, a GCS tier, or the underlying Sheets API.
Core principle: the cache is advisory. Backing is the source of truth. Failed cache operations degrade performance, never correctness.
TTL is owned by the cache layer, not the store. The store persists
structured values; the cache wrapper manages expiry via the per-rule ttl. An
expired entry is treated as a miss and re-fetched from the backing. Caching
works over any structured backing.
A store's byte-native file mode (config.file: true) is for serving raw
assets byte-exact, not for caching. The cache wraps structured stores, so
flow_validate warns when a store sets both file: true and cache. Drop one:
serve bytes with file: true and no cache, or cache a structured store with no
file.
When to use this skill
- A transformer reads the same key many times across events (sessions, user lookups, product catalog enrichment)
- A store has rate limits or slow HTTP round-trips (Sheets, custom API, S3
metadata);
@walkeros/server-store-apireads a third-party API, and its misses are not cached - You need to deduplicate concurrent reads on a cold key (thundering herd)
- You want to compose multi-tier caches (memory → GCS → Sheets)
Minimal recipe: cache a Sheets store
The talk-demo use case. A sessions lookup runs on every event but most events
in a session share the same key.
{
"stores": {
"sessions": {
"package": "@walkeros/server-store-sheets",
"config": {
"credentials": "$secret.SHEETS_CREDENTIALS",
"settings": {
"id": "1AbC...",
"sheet": "Sessions"
}
},
"cache": { "rules": [{ "ttl": 300 }] }
}
},
"transformers": {
"sessionLookup": {
"code": {
"type": "session-lookup",
"push": "$code:async (event, context) => { if (!event.user?.session) return; const session = await context.env.store.get(event.user.session); if (session) return { event: { ...event, data: { ...event.data, session } } }; }"
},
"env": { "store": "$store.sessions" }
}
}
}
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.
- 8d ago Changed · +1 lines 23067609c8bf
- 9d ago Changed · -5 lines 75f4404e0bef
- 1mo ago Changed · +19 lines 8cb7e14e1fe0
- 1mo ago Changed · +36 lines b5b9db77b8c6
- 2mo ago First seen · 371 lines · 56 tokens per session scan A d45cf0a4e64a
walkeros-using-store-cache is a skill published in the GitHub repository elbwalker/walkerOS (350 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 4,234 once invoked, about $0.0002 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-30.
walkeros-using-store-cache compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| walkeros-using-store-cacheelbwalker/walkerOS | Skill | 350 | today | MIT | A | 56 | Claude Code |
| orvalorval-labs/orval | Skill | 6.6k | yesterday | MIT | A | 83 | Claude Code, Codex |
| implementing-warehouse-sourcesPostHog/posthog | Skill | 41k | today | none | A | 83 | Claude Code, Codex |
| isolating-product-facade-contractsPostHog/posthog | Skill | 41k | today | none | A | 76 | Claude Code, Codex |
| django-migrationsPostHog/posthog | Skill | 41k | today | none | A | 99 | Claude Code, Codex |
| implementing-mcp-toolsPostHog/posthog | Skill | 41k | today | none | A | 58 | Claude Code, Codex |
| survey-sdk-auditPostHog/posthog | Skill | 41k | today | none | A | 30 | Claude Code, Codex |