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 instructions/redisearch/redisearch/claude-mdgit clone --depth 1 https://github.com/RediSearch/RediSearchWhat 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.00003 | $0.00003 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
RediSearch CLAUDE.md 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 1 lines · 3 tokens per session scan A a54ff182c7e8
RediSearch CLAUDE.md is an instructions file published in the GitHub repository RediSearch/RediSearch (6,228 stars, last pushed today), with no licence file. It adds 3 tokens to every session, about $0.0000 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 instructions, from other repositories
redis-vl-python CLAUDE.md
Instructions for redis/redis-vl-python, covering claude.md - redisvl project context, frequently used commands, development workflow, redis setup and documentation.
mcp-redis GEMINI.md
Instructions for redis/mcp-redis, covering redis mcp server extension, what this extension provides, available tools, string operations and hash operations.
Xapiand AGENTS.md
Instructions for Kronuz/Xapiand, covering agents.md — working in the xapiand codebase, first, the big split: own code vs. vendored, where things live, build & toggles and verifying changes end-to-end (the docs are a test suite).
memory AGENTS.md
Instructions for sunbeamdotpt/memory, covering sunbeam-memory — agent guide, project overview, runtime modes, semantic memory search (optional) and technology stack.
nestjs-starter copilot-instructions.md
Instructions for hmake98/nestjs-starter, covering nestjs starter — github copilot instructions, stack, directory layout, module wiring rules and guard order & auth decorators.
nestjs-starter prisma.instructions.md
Instructions for hmake98/nestjs-starter, a project described as: Production-ready NestJS boilerplate — JWT auth, Prisma, Redis, BullMQ, Swagger, i18n, and full AI developer workflows (Claude Code + GitHub Copilot) with spec-driven feature scaffolding.