review

A review checklist for adding and checking indexing features. An index is a searchable record that helps software find files, names, or other stored information quickly.

In plain words
What is it for?
Use it when reviewing a new index type: run the tests and type check, then verify invalidation, renaming, deletion, incremental updates, and search results.
Why use it?
It helps detect stale results, duplicate records, broken updates, and performance problems after files are changed, renamed, or deleted.

Command for Cursor

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.

agentmods
npx agentmods add commands/conradkoh/raggrep/review
Clone the repo
git clone --depth 1 https://github.com/conradkoh/raggrep

Made for: Cursor.

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,464 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01464
Opus 5 $0.00000 $0.00732
Sonnet 5 $0.00000 $0.00293
Haiku 4.5 $0.00000 $0.00146

Measured 2d ago against content hash 17346aa6dcc3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review 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 2d 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.

.cursor/commands/review.md · 230 lines

How it starts

The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Index Feature Review Checklist

Review checklist for new indexing features to ensure correctness, performance, and incremental update support.

Instructions

When adding a new index type (like literal index, reference index, etc.), run through this checklist to verify the implementation handles all edge cases correctly.

Pre-Flight Checks

Before reviewing the feature, ensure:

# Run all tests
bun test --timeout 180000

# Run TypeScript type check
bunx tsc --noEmit

Both must pass before proceeding with the review.

1. Index Invalidation & Staleness

File Modification

  • When a file is modified, old index entries are removed before new ones are added
  • Renamed identifiers (e.g., foobar) don't leave stale entries
  • Line number changes don't create duplicate entries with different chunk IDs

How to verify:

  1. Index a file with a function testFunc
  2. Rename testFunc to renamedFunc
  3. Re-index
  4. Search for testFunc - should return NO results
  5. Search for renamedFunc - should return the function

File Deletion

  • When a file is deleted, all its index entries are removed
  • No orphaned entries remain in secondary indexes (literal, symbolic, etc.)

How to verify:

  1. Index a file with identifiers
  2. Delete the file from disk
  3. Run index again (or cleanup)
  4. Verify the index file JSON is gone
  5. Verify secondary index entries are removed

Chunk ID Stability

  • Chunk IDs are deterministic (same content = same ID)
  • Chunk IDs change appropriately when content changes
  • Index correctly handles chunk ID changes on re-index

2. Incremental Updates

Efficiency

  • Only modified files are re-indexed (not the entire codebase)
  • finalize() doesn't rebuild the entire index from scratch
  • Secondary indexes support incremental updates (add/remove individual entries)

How to verify:

  1. Index a large folder
  2. Modify ONE file
  3. Re-index with --verbose
  4. Verify only 1 file shows as indexed (others show as unchanged)

Read the full file on GitHub · 230 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. 2d ago First seen · 230 lines · 0 tokens per session scan A 17346aa6dcc3

Subscribe to this mod's changes

review is a command published in the GitHub repository conradkoh/raggrep (22 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,464 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-30.