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/kouroshez/coding-os/redisnpx 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.svg" alt="Measured on agentmods" 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 | $0.00155 | $0.01388 |
| Opus 5 | $0.00077 | $0.00694 |
| Sonnet 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 3d 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.
- 3d 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.0008 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-31.
Other skills, from other repositories
omnigraph
Store, retrieve, and query knowledge, memory, and relationships in an Omnigraph graph, and operate a local or remote Omnigraph deployment. Use when the user wants to capture or recall facts, notes, or entities, build or query a knowledge graph or agent memory, or run Omnigraph — and whenever you see Omnigraph CLI…
fetch-data
取数 / 查数据 / 拉数据 / 跑 SQL。把自然语言取数需求转为 SQL，经数据湖仓执行后返回查询结果供下游分析。任何需要业务数据的任务在工作区缺少对应文件时都必须先调用此技能——覆盖 BI 业务分析、留存 / 转化 / 同期群分析、数据探索 EDA、统计建模、定量计算、元数据查询、数据查询。命中任一即触发：(1) 直接索要指标或记录，如「DAU 多少」「上月销售额」「3 月留存率」「这个客户的订单」；(2) 取数口语，如「查 / 查一下 / 取一下 / 拉一下 / 抓数据 / 找数据 / 搜数据 / 跑 SQL / 写 SQL / 导出 / 缺数据 / 没数据 / 数据不够」；(3) 涉及数据来源，如「从语义层 / 数据湖仓…
binder-modeling
Binder data modeling — define entity types, fields, relations, constraints, views, and navigation. Use when asked to "create a type", "add a field", "define a schema", "set up relations", "model entities", "create a view", "set up navigation", "render entities as files", or design a binder workspace schema.
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.
binder-import
Import external data into a Binder workspace. Handles CSV, JSON, YAML, Markdown files, and directories of Markdown. Use when asked to "import data", "load records from a file", "ingest documents", "migrate data into binder", or bulk-create records from an external source.
binder-cli
Binder CLI for knowledge graph operations — CRUD, search, schema inspection, transaction import, docs rendering. Use when asked to "query binder", "search records", "create a record", "check the schema", "import transactions", "undo changes", or work with a binder workspace.