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 kouroshez/coding-os --skill redisgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/redis)<a href="https://agentmods.dev/skills/kouroshez/coding-os/redis"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/redis/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/kouroshez/coding-os/redis"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/redis.svg" alt="Reviewed on agentmods" width="80" 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.00155 | $0.01388 |
| Opus 5.5 | $0.00062 | $0.00555 |
| Sonnet 5.5 | $0.00031 | $0.00278 |
| Haiku 4.5 | $0.00015 | $0.00139 |
Grade A, and why
redis 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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redis
Redis is fast because it's in-memory and ephemeral — treat it as a cache/derived store, never the source of truth. The craft is choosing the data structure that makes the operation O(1), the caching pattern that stays consistent with the database, and the eviction policy that fails gracefully when memory fills.
Summarize a verbose
redis-cli INFOinto health + flags:redis-cli INFO | python3 scripts/analyze_info.py
Pick the structure that fits the access
| Need | Structure | Why |
|---|---|---|
| cache one value / counter | String (GET/SET, INCR) |
atomic counter for free |
| object with fields | Hash (HSET/HGET) |
update one field without re-serializing |
| queue / recent list | List (LPUSH/RPOP) |
O(1) ends; BRPOP blocks for a worker |
| unique membership | Set (SADD/SISMEMBER) |
dedupe, set algebra |
| leaderboard / time-ordered | Sorted Set (ZADD/ZRANGE) |
score-ordered, O(log n) rank |
| event log / fan-out | Stream (XADD/XREAD) |
durable, consumer groups |
Using a String + JSON where a Hash fits means re-reading and re-writing the whole blob to change one field. Match the structure to the operation.
Cache-aside — the default pattern
def get_user(uid):
key = f"user:{uid}" # namespace:entity:id
cached = r.get(key)
if cached is not None:
return json.loads(cached) # hit
user = db.fetch_user(uid) # miss → source of truth
r.set(key, json.dumps(user), ex=300) # populate with a TTL — ALWAYS a TTL
return user
# Wrong — no TTL: stale forever, and the key never reclaims memory
r.set(key, value)
# Correct — every cache key has an expiry; staleness is bounded
r.set(key, value, ex=300)
On write, invalidate (r.delete(key)) rather than update the cache — let the
next read repopulate, so the cache can't drift from the DB. Patterns + write-through
trade-offs → references/patterns.md.
Atomicity — don't read-modify-write across round trips
What ships with it
5 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.
- 1mo ago First seen · 109 lines · 155 tokens per session scan A 108a945548f0
redis is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 155 tokens to every session and 1,388 once invoked, about $0.0006 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-31.
Other skills, from other repositories
brainctl
Unified agent memory CLI — read, write, search, and maintain the shared memory spine (brain.db). Use for persistent cross-session memory, knowledge graph, event logging, decisions, affect tracking, and consolidation.
slm-cache
KV cache for repeated reads — call slmcacheget(key) first; on a miss do the expensive operation then slmcacheset(key, value, ttlseconds) to store it; on a hit use the returned value directly; always fail-open (hit:false on any error, never raises); saves tokens when the same file, query result, or tool output is read…
guardian-cache
Store temporary agent state and cached API results in Redis using enforced mema: namespaces and TTL controls. Use when session data or expensive intermediate results must be shared across steps or sub-agents.
pinecone
Managed vector DB for production RAG and search.
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…
using-redis-token-buckets
Use when adding a bucket-like rate limit backed by Redis: a per-caller budget with burst capacity and continuous refill, a refund path for requests that did no work, or a limit whose Retry-After must be a real wait rather than a window edge. posthog/tokenbucket.py provides an atomic Lua token bucket (consume, refund…