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/usemoss/moss/zo-skillnpx skills add usemoss/moss --skill zo-skillgit clone --depth 1 https://github.com/usemoss/mossWhat 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.00048 | $0.01230 |
| Opus 5 | $0.00024 | $0.00615 |
| Sonnet 5 | $0.00010 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
moss-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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moss Search
Sub-10ms semantic search. Run from anywhere:
bash /home/workspace/Skills/moss-search/scripts/moss.sh load-index support-docs
bash /home/workspace/Skills/moss-search/scripts/moss.sh search support-docs "how long do refunds take?"
bash /home/workspace/Skills/moss-search/scripts/moss.sh create-index my-docs '[{"id":"1","text":"Refunds take 3-5 days."}]'
Commands
load-index
Download an index into memory for sub-10ms local queries. Always call this before searching an index for the first time.
bash /home/workspace/Skills/moss-search/scripts/moss.sh load-index <index-name>
Examples:
bash /home/workspace/Skills/moss-search/scripts/moss.sh load-index support-docs
bash /home/workspace/Skills/moss-search/scripts/moss.sh load-index code-docs
search
Search a loaded index. Sub-10ms after load-index.
bash /home/workspace/Skills/moss-search/scripts/moss.sh search <index-name> "<query>" [top_k]
Examples:
bash /home/workspace/Skills/moss-search/scripts/moss.sh search support-docs "how do I get a refund"
bash /home/workspace/Skills/moss-search/scripts/moss.sh search code-docs "authentication middleware" 10
create-index
Create a new index with initial documents.
bash /home/workspace/Skills/moss-search/scripts/moss.sh create-index <index-name> '<json-docs-array>'
Example:
bash /home/workspace/Skills/moss-search/scripts/moss.sh create-index faq '[{"id":"1","text":"Refunds take 3-5 business days."},{"id":"2","text":"Contact [email protected] for help."}]'
list-indexes
List all available indexes.
bash /home/workspace/Skills/moss-search/scripts/moss.sh list-indexes
add-docs
Add documents to an existing index.
bash /home/workspace/Skills/moss-search/scripts/moss.sh add-docs <index-name> '<json-docs-array>'
Example:
bash /home/workspace/Skills/moss-search/scripts/moss.sh add-docs faq '[{"id":"3","text":"Free shipping on orders over $50."}]'
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 · 157 lines · 48 tokens per session scan A 896e66e76579
moss-search is a skill published in the GitHub repository usemoss/moss (669 stars, last pushed 10d ago), licensed BSD-2-Clause. It adds 48 tokens to every session and 1,230 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-30.
Other skills, from other repositories
Hybrid Search Architect
Designs a hybrid retrieval pipeline combining dense vector search and BM25 sparse search with reciprocal rank fusion, and explains when to use each configuration.
nemotron-retrieval-recipes
Use when planning, debugging, tuning, evaluating, exporting, or deploying public Nemotron embed/rerank retrieval recipes.
mcp-local-rag
Searches, saves, and maintains a local document index through a local RAG MCP server. Use when user says "search my docs", "save this page", "read around that chunk", "sync my index", or invokes npx mcp-local-rag.
tao-finetune-cosmos-embed
Cosmos-Embed1 video-text embedding for text-to-video retrieval, video-to-video search, semantic deduplication, and fine-tuning. Use when the user asks to "fine-tune Cosmos-Embed1", "run cosmos-embed inference", "export Cosmos-Embed1", "embed videos", or "search videos with text".
pinecone:n8n
Build n8n workflows using the Pinecone Assistant node or Pinecone Vector Store node. Use when building RAG pipelines, chat-with-docs workflows, configuring Pinecone nodes in n8n, troubleshooting Pinecone n8n nodes, or asking about best practices for Pinecone in n8n.
pinecone:quickstart
Interactive Pinecone quickstart for new developers. Choose between two paths - Database (create an integrated index, upsert data, and query using Pinecone MCP + Python) or Assistant (create a Pinecone Assistant for document Q&A). Use when a user wants to get started with Pinecone for the first time or wants a guided…