SRA: Command for Claude Code

.agents/skills/upstash-redis-js/search/commands/index-management.md

index-management is a command for Claude Code from Aniket-a14/SRA. It costs 0 tokens per session (809 once invoked), scanned A, a copy of index-management, Apache-2.0.

A set of operations for creating, inspecting, waiting for, and deleting search indexes over Redis data. An index is a structured lookup that makes stored records searchable by defined fields.

In plain words
What is it for?
Use it to define JSON or hash indexes, inspect their schemas and settings, wait for indexing to finish, rebuild them, or remove them.
Why use it?
It helps keep search structures aligned with Redis keys, including after bulk data changes or when an index must be rebuilt.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents).

This is Aniket-a14/SRA's own configuration. It tells Claude Code how to work on SRA itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SRA configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Aniket-a14/SRA. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Aniket-a14/SRA/main/.agents/skills/upstash-redis-js/search/commands/index-management.md
Clone the repo
git clone --depth 1 https://github.com/Aniket-a14/SRA

Made for: Claude Code.

Wrote 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.

agentmods badge for index-management

README.md
[![agentmods](https://agentmods.dev/badge/commands/aniket-a14/sra/index-management/github.svg)](https://agentmods.dev/commands/aniket-a14/sra/index-management)
Your own site
<a href="https://agentmods.dev/commands/aniket-a14/sra/index-management"><img src="https://agentmods.dev/badge/commands/aniket-a14/sra/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.

agentmods 80×15 button for index-management

Your own site · 80×15
<a href="https://agentmods.dev/commands/aniket-a14/sra/index-management"><img src="https://agentmods.dev/badge/commands/aniket-a14/sra/index-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00809
Opus 5.5 $0.00000 $0.00324
Sonnet 5.5 $0.00000 $0.00162
Haiku 4.5 $0.00000 $0.00081

Measured 1mo ago against content hash ed83292d3c41, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

100% identical to index-management — 45 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/upstash-redis-js/search/commands/index-management.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 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.

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 with Options

const index = await redis.search.createIndex({
  name: "articles",
  prefix: ["article:", "post:"], // multiple prefixes
  dataType: "json",
  language: "english", // stemming language
  skipInitialScan: false, // scan existing keys (default)
  existsOk: true, // don't error if index already exists
  schema: s.object({
    title: s.string(),
    body: s.string().noStem(),
    publishedAt: s.date().fast(),
  }),
});

Get a Reference to an Existing Index

// If you already created the index and just need a reference
const index = redis.search.index({
  name: "products",
  schema: s.object({
    name: s.string(),
    price: s.number("F64"),
  }),
});

// Without schema (untyped - no filter/select type safety)
const untypedIndex = redis.search.index({ name: "products" });

Describe an Index

const description = await index.describe();
// {
//   name: "products",
//   dataType: "json",
//   prefixes: ["product:"],
//   language: "english",
//   schema: { name: { type: "TEXT" }, price: { type: "F64", fast: true } }
// }

// Returns null if index doesn't exist
const missing = await redis.search.index({ name: "nonexistent" }).describe();
// null

Read the full file on GitHub · 125 lines

Changes

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.

  1. 1mo ago First seen · 125 lines · 0 tokens per session scan A ed83292d3c41

Subscribe to this mod's changes

index-management is a command published in the GitHub repository Aniket-a14/SRA (24 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 809 tokens. A static security scan graded it A with 0 findings. It is 100% identical to index-management, differing in 45 lines, and is treated as a copy.