OpenCode is an open-source AI coding agent that helps developers work on software projects. It includes agents for full-access development, read-only exploration and planning, plus a general subagent for complex searches and multistep tasks; the catalogue add-ons extend its workflows.
Borrowing it
Nothing to install: this file belongs to anomalyco/opencode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anomalyco/opencode/dev/.opencode/skills/opencode-dev/SKILL.mdgit clone --depth 1 https://github.com/anomalyco/opencodeWrote 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/anomalyco/opencode/opencode-dev)<a href="https://agentmods.dev/skills/anomalyco/opencode/opencode-dev"><img src="https://agentmods.dev/badge/skills/anomalyco/opencode/opencode-dev/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/anomalyco/opencode/opencode-dev"><img src="https://agentmods.dev/badge/skills/anomalyco/opencode/opencode-dev.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.00057 | $0.03412 |
| Opus 5.5 | $0.00023 | $0.01365 |
| Sonnet 5.5 | $0.00011 | $0.00682 |
| Haiku 4.5 | $0.00006 | $0.00341 |
Grade A, and why
opencode-dev 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging opencode itself
Workflow for interactively exercising the CLI/TUI and server while developing in this repo. All commands below run from packages/cli unless noted otherwise.
Server/client model
opencode is a client/server system, not a single monolithic process:
- Server process runs the Effect HTTP API (
packages/server) and owns all domain state: sessions, database, plugins, permissions, Location services. It's started by theservecommand (packages/cli/src/commands/handlers/serve.ts). - TUI process is a separate process that runs no application logic itself — it's an HTTP/SSE client of the server via
@opencode/client(OpenCode.make). - Discovery: CLI processes find the shared server through a JSON registration file at
~/.local/state/opencode/service.json(orservice-local.jsonfor the local/dev channel) containing{id, version, url, pid, password}; the password is used for HTTP Basic auth. Before reusing a registration, the client callsGET /api/infoto confirm the server is alive, is the registered PID, and is version-compatible.opencode service statusprints the registered URL. - Sharing: because of this registration/health-check dance, many concurrent
opencode/TUI invocations converge on one shared background daemon rather than each spawning their own. If no compatible healthy daemon is found, a new one is spawned detached (serve --service) and registers itself. bun dev service start|status|stop|restartmanages this shared background daemon's lifecycle directly — useful when you need to force a fresh server, confirm one is running, or kill a stuck one.- Standalone mode (
--standalone) opts a single invocation out of the shared daemon: it spawns a private one-offserve --stdio --port 0child tied to that invocation's lifetime, with its own random password. Use this to isolate a debugging session from your other running opencode sessions. - Every log line is tagged
role=serverorrole=cliand a per-processrun=<id>, so you can distinguish server-side and client-side activity in one shared log file (see "Logs" below) even when both roles are interleaved from concurrent processes.
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.
- today Changed · -9 lines · -13 tokens per session 0a2a7df93e01
- 12d ago First seen · 232 lines · 70 tokens per session scan A a78570837a5d
opencode-dev is a skill published in the GitHub repository anomalyco/opencode (220,205 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 3,412 once invoked, about $0.0002 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-10-11.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…