add-opencode

add-opencode is a skill for Claude Code from nanocoai/nanoclaw. It costs 65 tokens per session (4,323 once invoked), scanned A, original, MIT.

An alternative agent provider that runs through OpenCode, a tool that can connect to models from services such as OpenRouter, OpenAI, Google, and DeepSeek. Each agent group can choose its provider separately.

In plain words
What is it for?
Use it to run selected agent groups with OpenCode. It adds the provider files, model and message handling, dependencies, and container integration.
Why use it?
It gives groups a provider choice beyond the default Claude setup. This can be useful when a group should use a different model service or provider configuration.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions OpenCode.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./container/build.sh build.

Good fit Use it to run selected agent groups with OpenCode. It adds the provider files, model and message handling, dependencies, and container integration.

Compare 6 skills from other repositories ↓
About the project

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.

nanocoai/nanoclaw · 30,980 stars · on GitHub · nanoclaw.dev

Install

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.

Clone the repo
git clone --depth 1 https://github.com/nanocoai/nanoclaw
agentmods
npx agentmods add skills/nanocoai/nanoclaw/add-opencode

Made for: Claude Code.

Wrote 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.

agentmods badge for add-opencode

README.md
[![agentmods](https://agentmods.dev/badge/skills/nanocoai/nanoclaw/add-opencode/github.svg)](https://agentmods.dev/skills/nanocoai/nanoclaw/add-opencode)
Your own site
<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/add-opencode"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/add-opencode/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.

agentmods 80×15 button for add-opencode

Your own site · 80×15
<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/add-opencode"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/add-opencode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,323 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 122
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 149
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.04323
Opus 5.5 $0.00026 $0.01729
Sonnet 5.5 $0.00013 $0.00865
Haiku 4.5 $0.00006 $0.00432

Measured yesterday against content hash b79cfd7ab826, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

add-opencode 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.

The scan reads SKILL.md. This mod also ships 37 executable files (payload/container/agent-runner/src/provider-contracts/opencode.ts, payload/container/agent-runner/src/providers/mcp-to-opencode.test.ts, payload/container/agent-runner/src/providers/mcp-to-opencode.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/add-opencode/SKILL.md · 345 lines

How it starts

The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenCode agent provider

Install OpenCode as an optional NanoClaw runtime. The payload is included in this skill; it needs no separate provider branch. It uses the upstream runtime, instructions, host, and setup metadata contracts. The host contract remains at version 1; the container owns its non-secret ChatGPT placeholder file.

OpenCode is offered by the standard setup provider picker. Existing installs can add or authenticate it with pnpm exec tsx setup/index.ts --step provider-auth opencode. To replace an installed payload and update its pins, append --refresh; back up local payload edits first. Ordinary re-authentication leaves installed files and the container image alone. Backend defaults are installation-wide; model and reasoning effort can be overridden per group through the existing container configuration. Per-group backend/auth selection and structured channel attachment transport are separate work.

Authentication checks the installed files, registration lines, and exact pins against this skill's declarations without launching a subprocess or container. Install and refresh run the existing provider contract verification; the build step owns image freshness. Model selection does not repeat installation checks. A working backend and account are checked separately by sending a real request.

Install

After installing this payload, run pnpm exec tsx scripts/opencode-host.ts --configure for host OpenCode setup, or use --update / --debug for the corresponding operational skill. An existing OpenCode CLI can also run directly in the checkout; it discovers .claude/skills natively. Host sign-in uses OpenCode's own settings and is independent of the container's gateway credentials. Installed setup failures use the existing provider failure-assist hook, including wizard authentication and installation-check failures. Host diagnostic context is model input and may remain in native OpenCode history; deleting its private temporary file does not erase those records. The helper requires stable OpenCode 1.18.25 or newer with --prompt and prefers the newest compatible installation it finds. --debug, --update and failure help launch it with an OPENCODE_PERMISSION override, so OpenCode asks before every edit and command even when the operator's top-level config allows them (OpenCode itself skips the prompt for a bare redirection with no command, such as > file). --configure keeps OpenCode's native permissions. Automatic help before payload installation is optional and is not part of the runtime contract.

Read the full file on GitHub · 345 lines

Files

What ships with it

41 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.

Changes

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.

  1. yesterday Changed b79cfd7ab826
  2. 21d ago Changed · -12 lines 58ded6581d30
  3. 22d ago Changed · +5 lines 920bbc6591a8
  4. 27d ago Changed · +19 lines 7e2968797bf1
  5. 1mo ago Changed · +92 lines bc480f10b3ce
  6. 1mo ago Changed · +6 lines 74178ac16aff
  7. 1mo ago First seen · 235 lines · 65 tokens per session scan A ccf74a3ec79e

Subscribe to this mod's changes

add-opencode is a skill published in the GitHub repository nanocoai/nanoclaw (30,980 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 4,323 once invoked, about $0.0003 per session on Opus 5.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-30.

Related

Other skills, from other repositories

Pynchy Development

Use when running pynchy locally — running the app, tests, linting, formatting, prek hooks, or rebuilding the agent container. Also use when determining whether you're on the live Pynchy host or a local machine, and for debugging agent behavior-- session transcript branching, inspecting message history and agent traces…

crypdick/pynchy · 79 tokens

Pynchy Plugin Authoring

Use when creating, scaffolding, or updating a pynchy plugin, including channels, MCP servers, skills, agent cores, workspace specs, and container runtime plugins. Also use when users ask how to register plugins via config.toml, add entry points, or validate plugin hook wiring.

crypdick/pynchy · 64 tokens

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.

crypdick/pynchy · 38 tokens

slack-token-extractor

Refresh expired Slack browser tokens (xoxc/xoxd) using persistent browser sessions. Use when Slack MCP tools fail with authentication errors.

crypdick/pynchy · 34 tokens

python-heredoc

When running multi-line Python code or code with quotes, apostrophes, or f-strings via Bash, always use heredoc syntax instead of python -c to avoid shell quoting issues.

crypdick/pynchy · 43 tokens

Documentation Manager

Use when writing or reviewing pynchy documentation, deciding where to document things, updating the docs, checking doc consistency, or fixing broken links. Covers information architecture, writing philosophy, tree-shaped navigation, doc-code coupling, no hard-coded usernames, extensibility framing for pluggable…

crypdick/pynchy · 68 tokens