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.
npx agentmods add skills/syntaxarc/archipy-plugin/redis-searchnpx skills add SyntaxArc/archipy-plugin --skill redis-searchgit clone --depth 1 https://github.com/SyntaxArc/archipy-pluginWrote 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/skills/syntaxarc/archipy-plugin/redis-search)<a href="https://agentmods.dev/skills/syntaxarc/archipy-plugin/redis-search"><img src="https://agentmods.dev/badge/skills/syntaxarc/archipy-plugin/redis-search.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00828 |
| Opus 5 | $0.00023 | $0.00414 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redis Search Skills
Overview
Redis search via ArchiPy (archipy[redis]):
- RediSearch: full-text via
RedisAdapter.search_index(name)→RedisSearchHandle - Vector search: KNN / range via
SearchQueryDTO.from_knn/from_range - Search caching: cache-aside around expensive search results
Canonical layout and ArchiPy constraints: ../archipy-docs/reference.md (Adapters + Redis Search). Templates:
reference/fulltext_adapter.py, reference/vector_adapter.py, reference/search_cache_adapter.py.
Before writing files
Ask the user for:
- Search type: full-text, vector, or caching
- Domain name (e.g.
product,document) - Data structure to index (HASH vs JSON)
- Search patterns needed (autocomplete, faceted search, …)
- Sync or async (or both as separate classes)
Prefer ArchiPy
uv add "archipy[redis]"
Thin domain wrapper around RedisAdapter.search_index() — not raw client.ft().
Key library symbols:
RedisAdapter.search_index(name)/list_search_indexes()- DTOs:
IndexSchemaDTO,TextFieldConfig,TagFieldConfig,NumericFieldConfig,VectorFieldConfig - Queries:
SearchQueryDTO,SearchQueryDTO.from_knn(...),SearchQueryDTO.from_range(...) - Documents:
HashDocumentUpsertDTO,JsonDocumentUpsertDTO - Types:
RedisIndexType,VectorAlgorithm,VectorDistanceMetric, … - Helpers:
pack_vector/unpack_vectorfromarchipy.adapters.redis.search
Requires Redis 8+ (query engine). Cluster needs hash-tagged prefixes (e.g. {products}:).
Generate
repositories/<domain>/
├── adapters/
│ └── <domain>_search_adapter.py # or _vector_ / _search_cache_
└── <domain>_repository.py
- Copy the matching template from
reference/, rename class/index/prefix to the domain. - Define a domain error (e.g.
ProductSearchError) undermodels/errors/— templates import it. - Wire via DI in
configs/containers.py. - Map Redis/RediSearch failures with
raise DomainError(...) from e.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 92 lines · 47 tokens per session scan A a233fdc92959
redis-search is a skill published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed 10d ago), licensed MIT. It adds 47 tokens to every session and 828 once invoked, about $0.0002 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.
Other skills, from other repositories
qdrant-monitoring-debugging
Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.
qdrant-scaling-query-volume
Guides Qdrant query volume scaling. Use when someone asks 'query returns too many results', 'scroll performance', 'large limit values', 'paginating search results', 'fetching many vectors', or 'high cardinality results'.
specx-add-infrastructure-adapter
Add technical infrastructure adapters for specx core scopes. Use when implementing SQLAlchemy repositories and Alembic-backed persistence, Redis stores, HTTP/network clients, file or queue adapters, unit-of-work implementations, gateway implementations for external APIs or SDKs such as OpenAI, or explicit diwire…
caching
HybridCache (.NET 9+), output caching, cache-aside pattern, and IMemoryCache — registration, usage, invalidation, and key strategy.
clean-architecture-testing
Use when it is unclear where a test belongs and what it is allowed to talk to — which test project and layer it goes in, whether it gets a real database, an in-memory fake, or no double at all, and whether a value object or a constructor is worth a test of its own. Also use when layer dependencies must be enforced by…
golang-samber-hot
In-memory caching in Golang using samber/hot — eviction algorithms (LRU, LFU, TinyLFU, W-TinyLFU, S3FIFO, ARC, TwoQueue, SIEVE, FIFO), TTL, cache loaders, sharding, stale-while-revalidate, missing key caching, and Prometheus metrics. Apply when using or adopting samber/hot, when the codebase imports…