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 superagents-lab/search1api-clinpx agentmods add plugins/superagents-lab/search1api-cli/marketplacegit clone --depth 1 https://github.com/superagents-lab/search1api-cliGrade A, and why
superagents-lab 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
{
"$schema": "https://json.schemastore.org/claude-code-marketplace.json",
"name": "superagents-lab",
"description": "Search1API plugins for live web research.",
"owner": {
"name": "Search1API",
"email": "[email protected]"
},
"plugins": [
{
"name": "search1api",
"source": "./",
"description": "Search the live web, read pages, find news, discover site links, and explore trending topics.",
"version": "1.0.0",
"author": {
"name": "Search1API",
"email": "[email protected]"
},
"homepage": "https://s1.dev/docs/integrations/skills",
"repository": "https://github.com/superagents-lab/search1api-cli",
"license": "MIT",
"category": "productivity",
"keywords": [
"search",
"research",
"news",
"crawl",
"fetch",
"mcp"
]
}
]
}
What ships with it
1 file beside marketplace.json 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.
- yesterday First seen · 34 lines scan A 3527de6c525d
superagents-lab is a plugin published in the GitHub repository superagents-lab/search1api-cli (2 stars, last pushed 7d ago), licensed MIT. 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
clasp
Develop Apps Script projects locally using clasp.
intlayer
Intlayer plugins for Claude Code — LSP-powered i18n intelligence for TypeScript, JavaScript, Vue, and Svelte projects.
mcp-vcf-orchestrator
Claude Code plugin marketplace for the VCF Automation Orchestrator MCP server: skills for discovery-first vRO authoring, package-first publishing, and guided operations.
osrs-wiki
OSRS Wiki MCP plugin marketplace.
jeremydev87
Plugin marketplace listing 1 plugin: codingbuddy.
graph-engineering
Runs coding work as an explicit execution graph (DAG) instead of a natural-language conversation. Deterministic work is executed by the server with zero LLM calls, the points where a human steps in are declared in the graph, and run state is owned by the server rather than the conversation.