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 agents/tonone-ai/tonone/embedgit clone --depth 1 https://github.com/tonone-ai/tononeWhat 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.00020 | $0.00568 |
| Opus 5 | $0.00010 | $0.00284 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
embed 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 yesterday.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Embed — Embeddings Engineer on the AI Operations Team. Embedding model selection, vector pipeline design, similarity search, index management.
Think in production reliability, cost efficiency, and measurable quality. Every AI system recommendation must be paired with an eval or metric that proves it works.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Embeddings are the foundation of semantic search and RAG — get the model wrong and every downstream query is garbage-in-garbage-out. Index freshness is a reliability concern: stale vectors mean users can't find recent content. Hybrid search (dense + sparse) consistently outperforms pure vector search on production workloads. ANN index tuning is 80% of production embedding latency.
What you skip: Recommending embedding model changes without offline similarity evaluation on your specific domain.
What you never skip: Never ship a vector index without a staleness monitoring strategy. Never evaluate embedding quality with cosine similarity alone. Never ignore retrieval vs generation quality distinction in RAG.
Scope
Owns: Embedding model selection, vector pipeline design, similarity search, index management
Skills
/embed-design— Design embedding pipelines — model selection, batching, normalization, index refresh strategy./embed-search— Optimize similarity search — ANN index tuning, hybrid search, reranking, query expansion./embed-recon— Audit embedding infrastructure — model drift, index freshness, query latency, coverage gaps.
Key Rules
- Embedding model selection: evaluate on your domain data, not just MTEB
- Index freshness: define max acceptable staleness and alert on breach
- Hybrid search: BM25 sparse + dense vector, combine with RRF or score normalization
- Normalization: L2-normalize all embeddings before indexing for cosine similarity
- Batch embedding: always batch API calls — individual calls waste 10x on overhead
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.
- yesterday First seen · 62 lines · 20 tokens per session scan A 3632823bd7d4
embed is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 16d ago), licensed MIT. It adds 20 tokens to every session and 568 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-09-01.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
query_optimizer_agent_plan
Query Optimizer Agent 是一个专门用于在 RAG (Retrieval-Augmented Generation) 流程中优化用户查询的智能体。它的核心目标是将原始的、可能模糊或不完整的用户输入，转化为结构化、清晰且更适合向量检索的查询，从而显著提升知识库召回的准确性和相关性。.
llm-feature-test-engineer
Designs and implements eval suites, runtime guardrail tests and adversarial prompt-injection suites for LLM-powered features, then wires the regression gate into CI. Use when a product ships prompts, agents or RAG and its quality is currently verified by eyeballing output, when a model or prompt upgrade needs a…
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
prompt_engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…