redis-search

A command that creates starter code for connecting an application to Redis search features. Redis is a data store that can also provide text search, meaning-based vector search, and cached results.

In plain words
What is it for?
Starting full-text search, vector search, or search caching for an application, including synchronous or asynchronous adapters and dependency-injection wiring.
Why use it?
It reduces the repeated setup needed to connect application code to Redis while keeping that connection behind a domain-specific adapter.

Command

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/syntaxarc/archipy-plugin/redis-search
Clone the repo
git clone --depth 1 https://github.com/SyntaxArc/archipy-plugin
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 145 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.00020 $0.00145
Opus 5 $0.00010 $0.00072
Sonnet 5 $0.00004 $0.00029
Haiku 4.5 $0.00002 $0.00015

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

Security

Grade A, and why

redis-search 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.

commands/redis-search.md · 15 lines

What it actually says

Follow the redis-search skill.

  1. Ask for search type (full-text / vector / caching), domain name, data structure, sync/async, and patterns needed.
  2. Prefer uv add "archipy[redis]" and a thin domain wrapper under repositories/<domain>/adapters/.
  3. Generate the matching adapter stub (s) + repository orchestrator stub if missing; wire via DI.

Docs: https://syntaxarc.github.io/ArchiPy/tutorials/adapters/ · bundled skills/archipy-docs/reference.md

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 · 15 lines · 20 tokens per session scan A fa7c7c5d7273

Subscribe to this mod's changes

redis-search is a command published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 145 once invoked, about $0.0001 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-31.