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/elbwalker/walkeros/walkeros-using-store-cachenpx skills add elbwalker/walkerOS --skill walkeros-using-store-cachegit clone --depth 1 https://github.com/elbwalker/walkerOSWhat 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 | $0.00056 | $0.03466 |
| Opus 5 | $0.00028 | $0.01733 |
| Sonnet 5 | $0.00011 | $0.00693 |
| Haiku 4.5 | $0.00006 | $0.00347 |
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 2d 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 — 371 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 Redis tier, or the underlying 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)
- You need to deduplicate concurrent reads on a cold key (thundering herd)
- You want to compose multi-tier caches (memory → Redis → API)
- You're migrating off
@walkeros/store-memory(removed in favor of the built-in tier)
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": "$var.sheetsCredentials",
"settings": {
"id": "1AbC...",
"sheet": "Sessions"
}
},
"cache": { "rules": [{ "ttl": 300 }] }
}
},
"transformers": {
"enrich": {
"package": "@walkeros/transformer-enrich",
"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.
- 2d 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 (343 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 3,466 once invoked, about $0.0003 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-30.
Other skills, from other repositories
azure-resource-manager-redis-dotnet
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) …
redis-inspect
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.
task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation.
caching
Caching strategies — invalidation, TTL guidelines, cache keys, cache layers, and when not to cache. Use when implementing or reviewing caching logic.
tanstack-ai-memory-redis
Use when wiring redis() from @tanstack/ai-memory/redis in production — covers client setup (ioredis or node-redis via fromNodeRedis), the storage model, client-side ranking limits, and troubleshooting.
redis-js
Work with the Upstash Redis JavaScript/TypeScript SDK for serverless Redis operations. Use for caching, session storage, rate limiting, leaderboards, full-text search (querying, filtering, aggregating with @upstash/redis search extension), and all Redis data structures. Supports automatic serialization/deserialization…