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.
git clone --depth 1 https://github.com/kinncj/HeimdallWrote 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/agents/kinncj/heimdall/redis)<a href="https://agentmods.dev/agents/kinncj/heimdall/redis"><img src="https://agentmods.dev/badge/agents/kinncj/heimdall/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.1 | $0.00018 | $0.00206 |
| Opus 5 | $0.00009 | $0.00103 |
| Sonnet 5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
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 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 28 lines · 18 tokens per session scan A e7e5e606bc33
redis is an agent published in the GitHub repository kinncj/Heimdall (65 stars, last pushed 4d ago), licensed AGPL-3.0. It adds 18 tokens to every session and 206 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
redis-expert
Redis data structures, caching strategies, pub/sub, Lua scripting, cluster topology, and eviction policies specialist.
backend-architect
Expert in backend system design, microservices architecture, event-driven patterns, caching strategies, database selection, and scalability patterns. Use when designing distributed systems, evaluating architectural trade-offs, or establishing back...
backend-engineer
Builds the backend for Sprint Zero — an Express, FastAPI, or Next.js API, or a CLI program — against the build configuration in docs/scope.md and the contract in docs/api-contract.md. Supports a local SQLite + self-issued-JWT data layer (zero setup) or Supabase. Invoked by the main Claude Code session during the build…
backend-platform-engineer
Implementation specialist for backend services. Use PROACTIVELY when the task involves NestJS, Node.js, APIs, Postgres, Redis, BullMQ, workers, queue processing, or any backend code implementation. Handles implementation after principal-engineer designs.
bullmq-expert
Expert in BullMQ task queue library for Node.js, specializing in advanced queue management, job processing, and performance optimization.
backend-dev
An agent for building and fixing server-side software, including APIs, business rules, databases, background jobs, authentication, and caching.