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 agentmods add skills/lanterncx/agent/using-opencodenpx skills add LanternCX/Agent --skill using-opencodegit clone --depth 1 https://github.com/LanternCX/AgentWhat 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 | $0.00036 | $0.00406 |
| Opus 5 | $0.00018 | $0.00203 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
using-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.
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
Using OpenCode
Use this when the task is about OpenCode itself rather than the user's app code.
Typical triggers:
- creating or editing an OpenCode
skill - creating or editing an OpenCode
command - creating or editing an OpenCode
agent - creating or editing an OpenCode
plugin - deciding where OpenCode-owned files should live
- checking whether project-level or global configuration is the better fit
Before you make changes, look up the current OpenCode docs and verify the expected location and format.
Docs to check first:
- Skills:
https://opencode.ai/docs/skills - Commands:
https://opencode.ai/docs/commands - Agents:
https://opencode.ai/docs/agents - Plugins:
https://opencode.ai/docs/plugins - Config and directory conventions:
https://opencode.ai/docs/config
While reading the docs, confirm these points before editing files:
- Whether the object should live in the project or global config.
- Which directory name is canonical (
skillsvsskill,commandsvscommand,agentsvsagent). - What file format is expected (
SKILL.md, markdown command file, markdown agent file, plugin source file, etc.). - Whether there is a minimum frontmatter or schema requirement.
Default behavior after checking the docs:
- Use the canonical OpenCode location when the docs are explicit.
- If the directory does not exist, create the minimum required structure.
- Prefer project-local paths when the user is asking for repo-specific behavior, unless they explicitly ask for a global install.
- If the docs and repository conventions disagree, mention the mismatch and follow the user's request.
Do not guess OpenCode-specific paths when the docs can answer the question.
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 · 44 lines · 36 tokens per session scan A 25a24f367e31
using-opencode is a skill published in the GitHub repository LanternCX/Agent (5 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 406 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…