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/upstash/redis-jsWrote 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/commands/upstash/redis-js/index-management)<a href="https://agentmods.dev/commands/upstash/redis-js/index-management"><img src="https://agentmods.dev/badge/commands/upstash/redis-js/index-management/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/commands/upstash/redis-js/index-management"><img src="https://agentmods.dev/badge/commands/upstash/redis-js/index-management.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.00000 | $0.01208 |
| Opus 5.5 | $0.00000 | $0.00483 |
| Sonnet 5.5 | $0.00000 | $0.00242 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
index-management 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 24d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- index-management — 100% identical, 45 lines differ
- index-management — 100% identical, 0 lines differ
- index-management — 100% identical, 45 lines differ
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Index Management
Overview
Create, inspect, and drop search indexes. Wait for indexing to complete after data changes. Indexes automatically track Redis keys matching a specified prefix, or the entries of a single stream.
Good For
- Creating indexes over existing or new Redis data
- Inspecting index schema and configuration
- Rebuilding or dropping indexes
- Ensuring data consistency after bulk writes
Examples
Create an Index
import { Redis, s } from "@upstash/redis";
const redis = Redis.fromEnv();
// JSON index with nested schema
const index = await redis.search.createIndex({
name: "products",
prefix: "product:",
dataType: "json",
schema: s.object({
name: s.string(),
price: s.number("F64"),
metadata: s.object({
brand: s.facet(),
tags: s.keyword(),
}),
}),
});
// Hash index (flat schema only)
const hashIndex = await redis.search.createIndex({
name: "sessions",
prefix: "session:",
dataType: "hash",
schema: {
userId: { type: "TEXT" as const },
lastActive: { type: "DATE" as const },
},
});
Create a Stream Index
A stream index is bound to one exact stream key (no prefix). Every entry added with XADD becomes a document whose key is the entry ID. The stream does not need to exist yet, and entries removed with XDEL/XTRIM (or by deleting the stream) leave the index too.
const events = await redis.search.createIndex({
name: "event-search",
dataType: "stream",
stream: "events", // exact stream key, not a prefix
schema: s.object({
message: s.string(),
service: s.keyword(),
severity: s.number("U64"),
occurredAt: s.date().fast(),
}),
});
await redis.xadd("events", "*", {
message: "Payment authorization failed",
service: "checkout",
severity: 4,
occurredAt: new Date().toISOString(),
});
await events.waitIndexing();
const hits = await events.query({
filter: { message: "authorization", severity: { $gte: 3 } },
});
// [{ key: "1757000000000-0", score: 0.5, data: { message: "...", service: "checkout", severity: 4, ... } }]
// Read the full original entry by its ID
const entries = await redis.xrange("events", hits[0].key, hits[0].key);
const entry = entries[hits[0].key];
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.
- 24d ago Changed · +41 lines 3c47248650f1
- 1mo ago First seen · 125 lines · 0 tokens per session scan A ed83292d3c41
index-management is a command published in the GitHub repository upstash/redis-js (980 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,208 tokens. 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 commands, from other repositories
laravel-performance-cache
Add caching to reduce work; use the laravel:performance-caching skill exactly as written.
gen-prisma-model
Add a new Prisma model to this codebase: $ARGUMENTS.
frappe-cache
Manage Redis cache - clear, monitor, and optimize Frappe cache performance.
database-scaling
Design database scaling strategy with read replicas, partitioning, and sharding recommendations.
implement-caching
Implement comprehensive multi-level API caching strategies with Redis, CDN, and intelligent invalidation.
cache
Hostile audit of caching correctness: assume every cache serves stale data after a write, shares a key across entities that must not share one, grows without bound, and stampedes on expiry — then prove where. A cache is a correctness liability until its key, its invalidation, its bound, and its expiry behavior are all…