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 maystudios/claude-skills --skill opencodegit clone --depth 1 https://github.com/maystudios/claude-skillsWrote 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/maystudios/claude-skills/opencode)<a href="https://agentmods.dev/skills/maystudios/claude-skills/opencode"><img src="https://agentmods.dev/badge/skills/maystudios/claude-skills/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.
<a href="https://agentmods.dev/skills/maystudios/claude-skills/opencode"><img src="https://agentmods.dev/badge/skills/maystudios/claude-skills/opencode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 36 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00174 | $0.05018 |
| Opus 5.5 | $0.00070 | $0.02007 |
| Sonnet 5.5 | $0.00035 | $0.01004 |
| Haiku 4.5 | $0.00017 | $0.00502 |
Grade A, and why
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 1mo 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.
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 — 521 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Sub-Agent Protocol
This is an executable protocol for delegating work to OpenCode agents. Follow it precisely.
Prerequisites
opencodeCLI installed and in PATH (verify:opencode --version)- At least one provider authenticated (
opencode providers list) - Available models listed via
opencode models
Core Command
OPENCODE_DISABLE_AUTOUPDATE=true opencode run --format json --model <provider/model> --agent <build|plan> --dir "<working-dir>" --dangerously-skip-permissions [options] "<prompt>" 2>/dev/null
Key flags:
--format json-- machine-parseable ndjson output (always use this)--model provider/model-- e.g.,openai/gpt-5.4,openai/gpt-5.3-codex--variant <level>-- reasoning effort:minimal,medium,high,xhigh(provider-specific)--dir <path>-- working directory for the task--dangerously-skip-permissions-- auto-approve tool calls (required for headless)-f/--file <path>-- attach file(s) to the prompt--agent <name>--buildfor implementation (filesystem+bash),planfor analysis (read-only)-c/--continue-- continue last session-s/--session <id>-- continue specific session
Output Parsing
The --format json flag emits ndjson (one JSON object per line):
| type | Contains |
|---|---|
text |
.part.text -- model's text response |
tool_call |
.part.name, .part.input -- tool invocations |
tool_result |
.part.output -- tool execution results |
step_start |
Session/message IDs |
step_finish |
.part.tokens (usage), .part.cost, .part.reason |
Parse with the helper script (always redirect stderr):
opencode run --format json ... 2>/dev/null | python .claude/skills/opencode/scripts/parse_output.py [--mode text|full|tools|cost|session|diff|summary]
Parse modes:
text-- model's text response (default)full-- text + tool calls + tool resultstools-- tool calls and results onlycost-- token usage and cost breakdownsession-- extract session ID for continuationdiff-- extract file modifications from tool callssummary-- one-line summary (status, tokens, cost, duration)
What ships with it
4 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.
- 1mo ago First seen · 521 lines · 174 tokens per session scan A 0eb4f8a3cdfd
opencode is a skill published in the GitHub repository maystudios/claude-skills (25 stars, last pushed 2mo ago), licensed MIT. It adds 174 tokens to every session and 5,018 once invoked, about $0.0007 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.
Other skills, from other repositories
timescaledb-hyperfunctions
Use this skill when writing analytical SQL over time-series data with the TimescaleDB Toolkit (timescaledbtoolkit extension) hyperfunctions: approximate percentiles, statistical summaries, time-weighted averages, counter/gauge rates, uptime/heartbeat tracking, state durations, OHLC candlesticks, approximate distinct…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
postgres
Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. Trigger when user asks to: Explore an existing PostgreSQL database to understand its objects and relationships Design or modify PostgreSQL tables…
postcss-best-practices
PostCSS best practices and configuration guidelines for modern CSS processing and optimization.
autogen-development
Expert guidance for Microsoft AutoGen multi-agent framework development including agent creation, conversations, tool integration, and orchestration patterns.
cloudflare-development
Cloudflare Workers, Pages, KV, D1, R2, and Durable Objects development best practices for edge computing applications.