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 skills add infino-ai/infino-mcp --skill using-infinogit clone --depth 1 https://github.com/infino-ai/infino-mcpWrote 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/infino-ai/infino-mcp/using-infino)<a href="https://agentmods.dev/skills/infino-ai/infino-mcp/using-infino"><img src="https://agentmods.dev/badge/skills/infino-ai/infino-mcp/using-infino/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/infino-ai/infino-mcp/using-infino"><img src="https://agentmods.dev/badge/skills/infino-ai/infino-mcp/using-infino.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00082 | $0.01348 |
| Opus 5 | $0.00041 | $0.00674 |
| Sonnet 5 | $0.00016 | $0.00270 |
| Haiku 4.5 | $0.00008 | $0.00135 |
Grade A, and why
using-infino 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 7d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Infino
Infino is a retrieval engine over data on object storage: full-text (BM25), vector, hybrid, and SQL search over one copy of the data, embedded in-process against a local path or bucket, or against a hosted Infino Cloud database. These tools (from the Infino MCP server) operate on a connected catalog of tables. The full toolset is always available; you are responsible for the data you change, and on Infino Cloud the API key's capabilities decide what the connection may do.
1. Discover before you search
infino_list_tables: list the tables in the catalog. Start here when you don't already know the table name. On a hosted connection a 404 here means the database does not exist yet: callinfino_create_database.infino_describe_table: a table's columns and types, so you know which column to target and what each result row carries. It does not report indexes; a search on a column with no index says so in its error.
2. Pick the search tool by the question shape
infino_keyword_search: literal terms such as identifiers, error codes, product names, exact phrases. Ranked BM25. Use when the wording is known.infino_semantic_search: meaning or paraphrase when the exact wording is unknown. Passfilter({column, query}) to first restrict to rows whose keyword column matches, then rank semantically within them.infino_hybrid_search: the query has both specific terms and an intent. Fuses keyword + vector in one ranking pass. A good default when unsure.infino_sql: structural or analytical questions: counts, GROUP BY, joins, aggregates, filtering by exact column value. The search functions are callable inside SQL too (bm25_search(...), andvector_search(...)with a{{name}}placeholder plusembed: {name: "text"}).infino_token_match/infino_exact_match/infino_count: unranked filters and a tally, when you need the set or the number, not an order.
Prefer the dedicated search tools over hand-written SQL for retrieval; they embed the query and project results for you.
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.
- 7d ago Changed · +44 lines · +17 tokens per session cd7ea061d208
- 11d ago First seen · 53 lines · 65 tokens per session scan A 15aab926cdc0
using-infino is a skill published in the GitHub repository infino-ai/infino-mcp (0 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 1,348 once invoked, about $0.0004 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
vector-databases
Vector database engineering covering Pinecone, Weaviate, Chroma, Qdrant, pgvector, and FAISS — including embedding pipeline design, HNSW index parameter tuning, hybrid dense+sparse (BM25) search, metadata filtering, namespace and tenant sharding, and RAG retrieval patterns for production knowledge systems.
pinecone:full-text-search
Create, ingest into, and query a Pinecone full-text-search (FTS) document index using the graduated document-schema API (Python SDK 10.0.0, API version 2026-07). Use when the user or agent asks to build a text search index on Pinecone, add dense or sparse vector fields, ingest documents, construct scoreby clauses…
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…
pinecone:cli
Guide for using the Pinecone CLI (pc) to manage Pinecone resources from the terminal. The CLI supports ALL index types (standard, integrated, sparse) and all vector operations — unlike the MCP which only supports integrated indexes. Use for batch operations, vector management, backups, namespaces, CI/CD automation…
pinecone:mcp
Reference for the Pinecone MCP server tools. Documents all available tools - list-indexes, describe-index, describe-index-stats, create-index-for-model, upsert-records, search-records, cascading-search, and rerank-documents. Use when an agent needs to understand what Pinecone MCP tools are available, how to use them…
pinecone
Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.