opencode

An OpenCode agent setup for OrangePro, a tool that prepares a repository with a behavior report, a requirements traceability matrix, and possible next actions. OpenCode is a coding agent that can use tools through an MCP server.

In plain words
What is it for?
Use it to prepare the current checkout, configure OrangePro as an OpenCode tool, and map a slash command such as /opro to the preparation step.
Why use it?
It provides a documented starting point for using OrangePro from OpenCode and explains how to connect the required local server.

Agent

Install

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.

agentmods
npx agentmods add agents/orangeproai/orangepro-mcp/opencode
Clone the repo
git clone --depth 1 https://github.com/OrangeproAI/orangepro-mcp
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 370 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00370
Opus 5 $0.00000 $0.00185
Sonnet 5 $0.00000 $0.00074
Haiku 4.5 $0.00000 $0.00037

Measured 2d ago against content hash 3de75a8994d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

docs/agents/opencode.md · 44 lines

What it actually says

OrangePro With OpenCode

Install

npm install -g @orangepro/orangepro-mcp
cd /path/to/your/repo
opro

opro is the one-command preparation step: behavior report, RTM, optional weak AI grounding and AI-suggested candidate flows when a provider key is configured, and next actions for the agent.

MCP Setup

Print the OpenCode MCP block:

opro agent --client opencode

Add the printed mcpServers.orangepro-local block to your OpenCode MCP settings. If OpenCode does not inherit your shell environment, put the model provider key in the local MCP config, or keep it in a repo-local .env.provider.local file that is not committed.

For a direct OpenCode config, add this server under mcp:

{
  "mcp": {
    "orangepro-local": {
      "enabled": true,
      "command": "npx",
      "args": ["-y", "@orangepro/mcp-server@latest", "mcp"]
    }
  }
}

If your OpenCode setup supports slash or dollar commands, map /opro or $opro to: call orangepro_start for the current checkout, then follow the returned next_actions. The shortcut should call the MCP tool; it is not a separate graph builder.

Agent Prompt

Use OrangePro first. Call orangepro_start, generate tests only through orangepro_generate_tests, write runnable tests with run_hints, run the command, and call `orangepro_prove` with the returned `prove_run` args after a pass for Dynamically Proven. Use record_run only for static diagnostics. Report setup failures plainly.
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. 2d ago First seen · 44 lines · 0 tokens per session scan A 3de75a8994d2

Subscribe to this mod's changes

opencode is an agent published in the GitHub repository OrangeproAI/orangepro-mcp (17 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 370 tokens. 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 agents, from other repositories

seo-ecommerce

E-commerce SEO analyst. Validates product schema, analyzes Google Shopping and Amazon marketplace visibility, identifies pricing gaps, and recommends product page optimizations. Spawned when e-commerce site detected during audits.

build-with-dhiraj/ai-workflow-framework-portability-kit · 43 tokens

trellis-check

Code quality check expert. Reviews code changes against specs and self-fixes issues.

yuqie6/ProductFlow · 20 tokens

strategy-consultant

You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…

modu-ai/moai-cowork · 106 tokens

speckit.analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

mbeacom/adrkit · 26 tokens

gtm-technical

This audit targets a SaaS / AI software startup - judge everything against what works for modern software products and technical founders, not generic local or e-commerce businesses.

adaptico/adaptico-os · 0 tokens

platform-engineer

Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.

ulises-jeremias/agent-toolkit · 88 tokens