Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tasict/opencode-plugin-cc/plugin install 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/tasict/opencode-plugin-cc/opencode-result-handling)<a href="https://agentmods.dev/skills/tasict/opencode-plugin-cc/opencode-result-handling"><img src="https://agentmods.dev/badge/skills/tasict/opencode-plugin-cc/opencode-result-handling/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/tasict/opencode-plugin-cc/opencode-result-handling"><img src="https://agentmods.dev/badge/skills/tasict/opencode-plugin-cc/opencode-result-handling.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.00028 | $0.01083 |
| Opus 5.5 | $0.00011 | $0.00433 |
| Sonnet 5.5 | $0.00006 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade C, and why
opencode-result-handling scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s http://localhost:4096/session/<sessionId>/message | python3 -c ' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:4096/session/<sessionId>/message How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Result Handling
Result Structure
OpenCode returns results as structured session data containing:
- Messages: The full conversation between the user prompt and OpenCode's agent
- Tool calls: All tool invocations (bash, edit, read, write, grep, glob, etc.)
- File changes: Diffs of all files modified during the session
- Status: Whether the session completed successfully, was aborted, or errored
Presenting Results
When displaying results from /opencode:result:
- Show the session ID for reference
- Present the final assistant message as the primary output
- If file changes were made, summarize which files were modified
- Include the session status (completed/aborted/error)
Resuming Sessions
OpenCode sessions can be resumed by sending additional messages to the same session.
The --resume-last flag in the companion script handles this by reusing the last session ID
from the current workspace state.
Inspecting Live Progress (while a task is still running)
A dispatched opencode task produces live progress in several layers — use the appropriate tool for the granularity you need.
Layer 1: Companion phase (coarse, whole-task)
Phase-level signals like starting → investigating → running → completed/failed. Useful to confirm the task is alive, not the specific work.
node "${CLAUDE_PLUGIN_ROOT}/scripts/opencode-companion.mjs" status <task-id> --json
Returns JSON with job.status, job.phase, job.elapsed, job.opencodeSessionId, and a progressPreview string (just phase-transition lines).
Layer 2: Full tool-call trace (fine, every action)
OpenCode runs a local HTTP server on http://localhost:4096 that exposes every message and tool call in every session. Hitting the messages endpoint gives you the complete live trace of what opencode is doing — bash commands it ran, file reads, edits, assistant reasoning text, tool results. This is the best signal for "what has opencode actually done so far."
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 · 90 lines · 28 tokens per session scan C 02db81392632
opencode-result-handling is a skill published in the GitHub repository tasict/opencode-plugin-cc (35 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,083 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…