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.
/plugin marketplace add infino-ai/infino-mcpnpx agentmods add plugins/infino-ai/infino-mcp/plugingit clone --depth 1 https://github.com/infino-ai/infino-mcpGrade A, and why
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 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.
What it actually says
{
"name": "infino",
"displayName": "Infino",
"description": "Keyword, vector, hybrid, and SQL retrieval over data on object storage, for AI agents.",
"version": "0.2.0",
"author": {
"name": "Infino",
"url": "https://github.com/infino-ai"
},
"homepage": "https://github.com/infino-ai/infino-mcp",
"repository": "https://github.com/infino-ai/infino-mcp",
"license": "Apache-2.0",
"keywords": [
"retrieval",
"search",
"vector",
"hybrid",
"bm25",
"sql",
"rag",
"agent-memory",
"object-storage",
"mcp"
],
"userConfig": {
"infino_uri": {
"type": "string",
"title": "Infino data URI",
"description": "Data to serve: a local path (e.g. /Users/me/.infino/memory), an s3://|gs://|az:// bucket URI, or a hosted https://<host>/<database> endpoint (Infino Cloud).",
"required": true
},
"infino_api_key": {
"type": "string",
"title": "Infino Cloud API key",
"description": "API key for a hosted https:// endpoint. Leave blank for a local path or bucket URI.",
"required": false
},
"enable_writes": {
"type": "boolean",
"title": "Enable writes",
"description": "Expose the add/update/delete tools and allow DDL/DML through SQL. Leave off for a read-only server.",
"default": false
}
}
}
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 · 46 lines scan A 6dad00b8ab4f
infino is a plugin published in the GitHub repository infino-ai/infino-mcp (0 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.