NanoClaw is an AI assistant that runs agents inside separate Linux containers, isolating their files and execution environments. People use it to connect agents to messaging services and run assistants with memory and scheduled jobs. The catalogue contains skills and instructions for extending or operating NanoClaw.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nanocoai/nanoclawnpx agentmods add skills/nanocoai/nanoclaw/add-tavily-toolWrote 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/nanocoai/nanoclaw/add-tavily-tool)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/add-tavily-tool"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/add-tavily-tool/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/nanocoai/nanoclaw/add-tavily-tool"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/add-tavily-tool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00041 | $0.01767 |
| Opus 5 | $0.00020 | $0.00883 |
| Sonnet 5 | $0.00008 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
add-tavily-tool scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Gate the deeplink: `curl -fs <dashboard-url>/connections/custom` must return How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Tavily Tool
Install the pinned mcp-remote bridge in the agent image and register Tavily's
remote MCP server for each selected agent group. The MCP server supplies its
tool descriptions and input schemas at runtime.
The registered server exposes:
mcp__tavily__tavily_searchmcp__tavily__tavily_extract
The registration is provider-agnostic: any provider with MCP support picks it
up (Claude, OpenCode, and Codex all do). Groups on the Claude provider already
have the built-in WebSearch and WebFetch tools
(container/agent-runner/src/providers/claude.ts), so the skill adds the most
for groups on other providers, and for Tavily's structured extraction
anywhere.
Phase 1: Pre-flight
Check whether the bridge is already in the image manifest, then list the groups:
grep -n '"mcp-remote"' container/cli-tools.json || true
ncl groups list
Ask which agent groups should receive Tavily. If mcp-remote is already
present at a pinned version, reuse the existing entry instead of adding a
second one.
Phase 2: Install the MCP bridge
Add this object to the top-level array in container/cli-tools.json when an
entry named mcp-remote is not already present:
{
"name": "mcp-remote",
"version": "0.1.38"
}
Keep the JSON valid and limit the entry to the two fields shown; this package does not require a native build-script opt-in.
Copy the dependency guard into the host test tree:
cp .claude/skills/add-tavily-tool/tavily-manifest.test.ts src/tavily-manifest.test.ts
Build the image and run the guard:
./container/build.sh
pnpm exec vitest run src/tavily-manifest.test.ts
The manifest is the only source-backed integration point. Per-group MCP
registration is runtime state stored through ncl, so it has no in-tree line
for a registration test to guard.
Phase 3: Register Tavily
config add-mcp-server and groups restart are approval-gated. Run from
inside a container they return approval-pending immediately; that is not an
error. Wait for the admin's approval and the follow-up system message before
moving on to Phase 4.
What ships with it
3 files 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.
- 11d ago First seen · 179 lines · 41 tokens per session scan A 33004bd8cd0e
add-tavily-tool is a skill published in the GitHub repository nanocoai/nanoclaw (30,736 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,767 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
x-integration
Post tweets, like, reply, retweet, and quote on X (Twitter) using browser automation. Use when the user asks you to interact with X/Twitter.
slack-token-extractor
Refresh expired Slack browser tokens (xoxc/xoxd) using persistent browser sessions. Use when Slack MCP tools fail with authentication errors.
computer-use
Drive a host desktop through Pynchy's policy-mediated provider plugins when browser automation is inappropriate.
browser-control
How to use browser tools for web navigation and interaction.
browser-cdp
Use this skill when you need to control a Chrome browser via CDP (Chrome DevTools Protocol) to reuse existing login sessions. Covers: launching Chrome in debug mode, opening URLs, waiting for page load, evaluating JavaScript, taking snapshots, and extracting auth tokens. Trigger phrases: browser automation, CDP…
pm-preview
A tool that previews Markdown product documents in a web browser and refreshes the view when the documents change. Markdown is a plain-text format commonly used for project documentation.