walkeros-using-store-cache

walkeros-using-store-cache is a skill for Claude Code from elbwalker/walkerOS. It costs 56 tokens per session (4,234 once invoked), scanned A, original, MIT.

A guide to adding a read-through, write-through cache around a walkerOS store. A cache keeps temporary copies of structured data so repeated reads can avoid the slower backing system, while the backing remains the source of truth.

In plain words
What is it for?
Use it to cache store reads, choose expiration times, connect memory or Redis-like tiers, define error handling, and monitor cache activity.
Why use it?
It reduces repeated slow API or spreadsheet reads and can handle multiple cache levels or simultaneous requests without changing the code that reads the store.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the walkeros plugin — 24 skills, 2 MCP servers shipped together

Good fit Use it to cache store reads, choose expiration times, connect memory or Redis-like tiers, define error handling, and monitor cache activity.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/elbwalker/walkeros/walkeros-using-store-cache
Install

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.

Any agent
npx skills add elbwalker/walkerOS --skill walkeros-using-store-cache
Clone the repo
git clone --depth 1 https://github.com/elbwalker/walkerOS

Made for: Claude Code.

Or install walkeros, the plugin that ships this one along with the rest of its 24 skills, 2 MCP servers.

Wrote 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.

agentmods badge for walkeros-using-store-cache

README.md
[![agentmods](https://agentmods.dev/badge/skills/elbwalker/walkeros/walkeros-using-store-cache/github.svg)](https://agentmods.dev/skills/elbwalker/walkeros/walkeros-using-store-cache)
Your own site
<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.

agentmods 80×15 button for walkeros-using-store-cache

Your own site · 80×15
<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>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,234 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 23067609c8bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/walkeros-using-store-cache/SKILL.md · 422 lines

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-api reads 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" }
    }
  }
}

Read the full file on GitHub · 422 lines

Changes

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.

  1. 8d ago Changed · +1 lines 23067609c8bf
  2. 9d ago Changed · -5 lines 75f4404e0bef
  3. 1mo ago Changed · +19 lines 8cb7e14e1fe0
  4. 1mo ago Changed · +36 lines b5b9db77b8c6
  5. 2mo ago First seen · 371 lines · 56 tokens per session scan A d45cf0a4e64a

Subscribe to this mod's changes

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.

Related

walkeros-using-store-cache compared with skills from other repositories

walkeros-using-store-cache next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
walkeros-using-store-cacheelbwalker/walkerOSSkill350todayMITA56Claude Code
orvalorval-labs/orvalSkill6.6kyesterdayMITA83Claude Code, Codex
implementing-warehouse-sourcesPostHog/posthogSkill41ktodaynoneA83Claude Code, Codex
isolating-product-facade-contractsPostHog/posthogSkill41ktodaynoneA76Claude Code, Codex
django-migrationsPostHog/posthogSkill41ktodaynoneA99Claude Code, Codex
implementing-mcp-toolsPostHog/posthogSkill41ktodaynoneA58Claude Code, Codex
survey-sdk-auditPostHog/posthogSkill41ktodaynoneA30Claude Code, Codex