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 superagents-lab/search1api-cli --skill search1apigit clone --depth 1 https://github.com/superagents-lab/search1api-cliWrote 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/superagents-lab/search1api-cli/search1api)<a href="https://agentmods.dev/skills/superagents-lab/search1api-cli/search1api"><img src="https://agentmods.dev/badge/skills/superagents-lab/search1api-cli/search1api/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/superagents-lab/search1api-cli/search1api"><img src="https://agentmods.dev/badge/skills/superagents-lab/search1api-cli/search1api.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.00194 | $0.04396 |
| Opus 5.5 | $0.00078 | $0.01758 |
| Sonnet 5.5 | $0.00039 | $0.00879 |
| Haiku 4.5 | $0.00019 | $0.00440 |
Grade C, and why
search1api scanned grade C with 2 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 5d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://cli.search1api.com/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://cli.search1api.com/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search1API
Live web research through the s1 command-line tool.
Prerequisites
Every command in this skill runs through s1. Check that it is installed and
authenticated:
s1 balance
If the command is not found, install it:
curl -fsSL https://cli.search1api.com/install.sh | bash
Or via npm:
npm install -g search1api-cli
Then authenticate — prefer browser login, so no key is pasted into the conversation:
s1 login
Manual fallback:
s1 config set-key <your-api-key>
You can also set the environment variable SEARCH1API_KEY.
Do not install anything when s1 already works. To update an existing install,
the user can run s1 update — only suggest this when a command fails in a
version-related way.
If s1 is not found after installing, check that the npm global bin directory
is on PATH. npx -y search1api-cli <command> works as a fallback without any
install:
npx -y search1api-cli balance
Auth and credit errors are terminal. When a command reports an invalid key
or insufficient credits, confirm the state once with s1 balance, then tell the
user what is blocking and stop. Retrying the same command returns the same
error.
When to use
| User intent | Command |
|---|---|
| Shares a URL / link → read and summarize | s1 crawl <url> |
| Wants to search the web | s1 search "<query>" |
| Asks a question that spans sources, unsure where to look | s1 ask "<question>" |
| Wants the full page behind a search result | s1 crawl <url> |
| Wants news | s1 news "<query>" |
| Wants to explore a site's links | s1 sitemap <url> |
| Wants trending topics | s1 trending <service> |
| Wants to check remaining credits | s1 balance |
| Wants an agent to keep a URL for later use | s1 learn <url> |
Read it once, or learn it for good?
These look similar and are not:
- "What does this page say?", "summarize this link", "read these docs and
answer X" →
s1 crawl. One page, answer now, nothing written to disk. - "Learn this URL", "make a skill out of these docs", "记住这个文档" →
s1 learn. Produces an installable skill directory the user's agent can load later. - Scope follows the request. A single link is one page; a documentation set
("learn these docs", "学一下 XX 文档") is
--sitepointed at its root — that is the normal case, not an escalation. When it is genuinely unclear, run--discoverand show the user what a full run would cover.
What ships with it
1 file 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.
- 5d ago Changed · +1 lines fdd2adbc9f4f
- 7d ago Changed · +32 lines · +4 tokens per session 75207ad2c47f
- 1mo ago Changed · +2 lines · -19 tokens per session 505aa6a93697
- 1mo ago First seen · 369 lines · 209 tokens per session scan C d991691275e2
search1api is a skill published in the GitHub repository superagents-lab/search1api-cli (2 stars, last pushed 6d ago), licensed MIT. It adds 194 tokens to every session and 4,396 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
search1api
Multi-engine web research through Search1API. Search general web engines and specialized sources such as GitHub, Reddit, X, arXiv, Wikipedia, YouTube, WeChat, and Bilibili; read pages, find news, explore site links, and answer with cited sources. Use when the user requests web research, a source-specific search…
browser-use
Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.
repro-public
Reproduce a bug in the public-facing rendered site (not the admin). Attach a container, start the demo dev server, drive public routes with agent-browser, and capture the reproduction as screenshots plus a replayable transcript.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
web-scraping
Fetches web pages and extracts structured data using mq's toolchain (mq-crawl for fetching/crawling/JS rendering, mq for HTML-to-Markdown selector-based extraction, http() for in-query requests). Use when the user wants to scrape a URL, pull structured data out of a webpage, crawl a site, or turn HTML into…
adding-a-command
Creates a new CLI command following the Commander.js pattern in src/commands/. Handles command registration in src/cli.ts, telemetry tracking via tracked() wrapper, and option parsing. Use when user says add command, new CLI command, create subcommand, or adds files to src/commands/. Do NOT use for modifying existing…