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/srini047/haystack-skills/haystacknpx skills add srini047/haystack-skills --skill haystackgit clone --depth 1 https://github.com/srini047/haystack-skillsWhat 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.00055 | $0.01316 |
| Opus 5 | $0.00028 | $0.00658 |
| Sonnet 5 | $0.00011 | $0.00263 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
haystack 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Haystack
This skill is for building intelligent search and retrieval systems with Haystack, combining document processing, semantic search, and LLM integration.
Overview
This skill provides guidance for working with Haystack 2.0+, a modern framework for building production-grade RAG and search applications. Haystack enables building systems that combine:
- Document processing and indexing
- Semantic and hybrid search capabilities
- LLM integration for question-answering and reasoning
- Multi-stage pipelines for complex workflows
- Vector and keyword-based retrieval strategies
When to use
Use this skill when the user is working on:
- Building RAG Systems: Creating retrieval-augmented generation pipelines that combine document search with LLM reasoning
- Document Search & Indexing: Implementing semantic or hybrid search over document collections
- Question-Answering Systems: Building QA systems that retrieve relevant context and answer questions
- LLM Integration: Connecting language models with retrieval systems for grounded responses
- Pipeline Development: Creating multi-stage processing workflows with Haystack components
- Document Processing: Preparing, chunking, and indexing documents for retrieval
- Vector Store Setup: Configuring and managing document embeddings and vector databases
Core Concepts
Key Haystack Components
- DocumentStore: Storage backends for documents (ElasticsearchDocumentStore, InMemoryDocumentStore, WeaviateDocumentStore, etc.)
- Retriever: Components that fetch relevant documents (BM25Retriever, EmbeddingRetriever, HybridRetriever)
- Pipeline: DAG-based orchestration of components
- Generators/Answerers: LLM-powered components that generate responses
- Preprocessors: Components for text chunking, cleaning, and normalization
Architecture Patterns
1. Simple RAG Pipeline
Query → Retriever → LLM Generator → Answer
2. Hybrid Search Pipeline
Query → BM25 Retriever ⟶ Embedding Retriever ⟶ Document Joiner → LLM Generator → Answer
What ships with it
6 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.
- 2d ago First seen · 179 lines · 55 tokens per session scan A 54f9de9098cd
haystack is a skill published in the GitHub repository srini047/haystack-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,316 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.