index-management

index-management is a command for Claude Code from frontal-labs/mcp-server. It costs 0 tokens per session (1,208 once invoked), scanned A, original, Apache-2.0.

Commands for creating and managing search indexes, which are structures that make stored data searchable. They can inspect, rebuild, wait for, or remove indexes over Redis keys or stream entries.

In plain words
What is it for?
Use them to create indexes for JSON, hash, or stream data, inspect their setup, wait for indexing to finish, and drop or rebuild indexes.
Why use it?
They help keep searchable data aligned with the underlying records, especially after bulk changes. They also provide a way to control the fields and data types used for searches.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use them to create indexes for JSON, hash, or stream data, inspect their setup, wait for indexing to finish, and drop or rebuild indexes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/frontal-labs/mcp-server/index-management
Install

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.

Clone the repo
git clone --depth 1 https://github.com/frontal-labs/mcp-server

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/frontal-labs/mcp-server/index-management/github.svg)](https://agentmods.dev/commands/frontal-labs/mcp-server/index-management)
Your own site
<a href="https://agentmods.dev/commands/frontal-labs/mcp-server/index-management"><img src="https://agentmods.dev/badge/commands/frontal-labs/mcp-server/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/frontal-labs/mcp-server/index-management"><img src="https://agentmods.dev/badge/commands/frontal-labs/mcp-server/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 1,208 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 original No closer match found 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.01208
Opus 5.5 $0.00000 $0.00483
Sonnet 5.5 $0.00000 $0.00242
Haiku 4.5 $0.00000 $0.00121

Measured yesterday against content hash 3c47248650f1, 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 yesterday.

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.

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

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];

Read the full file on GitHub · 166 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. yesterday First seen · 166 lines · 0 tokens per session scan A 3c47248650f1

Subscribe to this mod's changes

index-management is a command published in the GitHub repository frontal-labs/mcp-server (1 stars, last pushed yesterday), licensed Apache-2.0. 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-10-15.