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/davidbudnick/redis-tui/claude-mdgit clone --depth 1 https://github.com/davidbudnick/redis-tuiWrote 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/instructions/davidbudnick/redis-tui/claude-md)<a href="https://agentmods.dev/instructions/davidbudnick/redis-tui/claude-md"><img src="https://agentmods.dev/badge/instructions/davidbudnick/redis-tui/claude-md.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.01773 | $0.01773 |
| Opus 5 | $0.00886 | $0.00886 |
| Sonnet 5 | $0.00355 | $0.00355 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
redis-tui 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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
Redis TUI Manager — a terminal user interface for managing Redis databases, built with Go and Bubble Tea. Alternative to redis-cli with interactive browsing, editing, monitoring, and advanced operations.
Build & Test Commands
make build # Build binary to bin/redis-tui
make test # Run tests: go test -v ./...
make bench # Hot-path benchmarks (key scans, preview fetches, rendering)
make test-cover # Tests with coverage report
make lint # Run go vet
make fmt # Format code with go fmt
make run # Build and run the application (make start is an alias)
make dev-deps # Install goreleaser
make test-cover-check # Tests + fail if any function < 100% coverage
make ci # Full local pipeline — run before every push
Run make ci before every push. It is the local stand-in for GitHub Actions: gofmt + go vet + go test -race with 100% function coverage, gosec, govulncheck, cross-compile for linux/darwin/windows, compile tests as GOOS=windows, and the Ubuntu 26.04 cross-device update repro (needs Docker). Do not push until it is green. CI also runs that same suite on Ubuntu, macOS, and Windows hosts — Unix-only tests must skip or stay portable on Windows.
CI runs go test -v -race -coverprofile=coverage.out ./... — always ensure tests pass with -race. CI enforces 100% statement coverage per function — any new code must include tests.
Architecture
main.go # Entry point, CLI flag parsing, config init
internal/
cmd/ # Bubble Tea command factories (return tea.Cmd)
ui/ # Bubble Tea UI (Model/Update/View pattern)
redis/ # Redis client wrapper (standalone + cluster)
types/ # Shared type definitions and messages
db/ # Config persistence (~/.config/redis-tui/config.json)
service/ # Interfaces (ConfigService, RedisService) and DI container
testutil/ # Test helpers and mock implementations
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.
- 6d ago First seen · 107 lines · 1,773 tokens per session scan A 3f04a43c7296
redis-tui CLAUDE.md is an instructions file published in the GitHub repository davidbudnick/redis-tui (44 stars, last pushed 4d ago), licensed MIT. It adds 1,773 tokens to every session, about $0.0089 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
RedisInsight CLAUDE.md
Claude Code instructions for redis/RedisInsight, a project described as: Redis GUI by Redis.
swarmcode CLAUDE.md
Claude Code instructions for spranab/swarmcode, covering swarmcode, architecture, key design, running and environment.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
cc-use-exp redis-safety.instructions.md
Instructions for doccker/cc-use-exp, covering redis 安全规范, 禁止操作, 必须遵守 and 嗅探信号.
cachey CLAUDE.md
Instructions for s2-streamstore/cachey, a project described as: Read-through cache for object storage.
cachey GEMINI.md
Instructions for s2-streamstore/cachey, a project described as: Read-through cache for object storage.