opro

opro is a skill for Claude Code from OrangeproAI/orangepro-mcp. It costs 18 tokens per session (263 once invoked), scanned A, original, MIT.

Instructions for using OrangePro to find missing behavioral tests and generate repository-specific tests. OrangePro is a tool that analyzes local code and runtime evidence.

In plain words
What is it for?
Finding high-priority test gaps, generating runnable tests, running them in the correct package, and recording whether the behavior was proven or covered.
Why use it?
They distinguish tests that are actually proven from suggestions or indirect signals, helping avoid claiming coverage that was never verified.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the orangepro plugin — 1 skill, 1 MCP server shipped together

Good fit Finding high-priority test gaps, generating runnable tests, running them in the correct package, and recording whether the behavior was proven or covered.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orangeproai/orangepro-mcp/opro
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.

Any agent
npx skills add OrangeproAI/orangepro-mcp --skill opro
Clone the repo
git clone --depth 1 https://github.com/OrangeproAI/orangepro-mcp

Made for: Claude Code.

Or install orangepro, the plugin that ships this one along with the rest of its 1 skill, 1 MCP server.

Wrote 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.

agentmods badge for opro

README.md
[![agentmods](https://agentmods.dev/badge/skills/orangeproai/orangepro-mcp/opro.svg)](https://agentmods.dev/skills/orangeproai/orangepro-mcp/opro)
Your own site
<a href="https://agentmods.dev/skills/orangeproai/orangepro-mcp/opro"><img src="https://agentmods.dev/badge/skills/orangeproai/orangepro-mcp/opro.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 263 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00018 $0.00263
Opus 5 $0.00009 $0.00131
Sonnet 5 $0.00004 $0.00053
Haiku 4.5 $0.00002 $0.00026

Measured 8d ago against content hash 8cba79a973f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

opro 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 8d 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.

plugins/orangepro/skills/opro/SKILL.md · 18 lines

What it actually says

Use the OrangePro MCP tools for local evidence-graph analysis and grounded test generation.

  1. Start with orangepro_start for the current checkout.
  2. If OrangePro reports a large-repo scope breakdown, prefer a focused scope for AI/generation; full deterministic analysis is still allowed.
  3. For PR work, call orangepro_generate_tests with base_ref=main.
  4. For baseline work, call orangepro_find_test_gaps, pick one high-priority gap, then call orangepro_generate_tests for that target.
  5. Write only generated tests that include run_hints; drafts are context, not runnable claims.
  6. Run the suggested command from the owning package directory.
  7. After a pass, call the returned prove_run args so OrangePro can dynamically prove the target. Use record_run only for static diagnostics.
  8. Report status as Proven, Reproven, Runtime-covered, Associated signal, or No link. Never promote Associated signal or AI links to Proven.

OrangePro may use weak AI grounding when a provider key is configured, but AI links are suggestions for generation only and never change Proven coverage.

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. 8d ago First seen · 18 lines · 18 tokens per session scan A 8cba79a973f8

Subscribe to this mod's changes

opro is a skill published in the GitHub repository OrangeproAI/orangepro-mcp (17 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 263 once invoked, about $0.0001 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-30.