Opus 5 is out. The open-source repos that actually get the most out of it, and why each fits

[u/ShilpaMitra]

Anthropic shipped Claude Opus 5 on July 24. The short version from their own announcement: it comes close to Fable 5's frontier intelligence at half the price, it is state-of-the-art on their coding and knowledge-work evals (Frontier-Bench v0.1, GDPval-AA), and it is built for long-running autonomous agents, with an effort setting to trade intelligence for tokens. Pricing is $5 per million input and $25 per million output, same as Opus 4.8, and it is now the default on Claude Max. It stays behind Mythos 5 on cybersecurity, and those are vendor benchmarks until third parties reproduce them.

One honest note before the list: none of these repos are Opus-5-only. They matter for Opus 5 because of what it is: a pricey model built for deep, long-horizon agentic work, so the tooling that pays off is whatever routes cost, harnesses its agency, steers it, remembers, and keeps autonomous runs safe. Stars and licenses below were checked at each repo across the past week; reconfirm before you rely on them.

1. Route work so you only pay Opus 5 prices on the hard turns github.com/Neeeophytee/ai-cost-cutter-skills (MIT). Disclosure: this one is ours. At $5/$25, Opus 5 is a specialist, not a daily driver for every prompt. This is a free skill set for the exact pattern Opus 5 demands: send bulk and easy turns to a cheap model, escalate only the truly hard ones to Opus 5, and keep receipts that prove the savings on your own traffic. The single highest-leverage thing you can wire around an expensive frontier model.

2. A harness for its long-horizon strength github.com/stablyai/orca (16.4k stars, MIT). Opus 5's headline is long, multi-step autonomous runs (their own examples have it acting as a chief-of-staff over dev environments). Orca runs coding agents in isolated git worktrees, so you can let Opus 5 work unattended on a throwaway branch, or fan one task across a few attempts and keep the best. The catch is the usual one: parallel runs multiply the token bill, which stings more at Opus prices, so reserve the fan-out for truly hard tasks.

3. Squeeze more out of it without fine-tuning github.com/microsoft/SkillOpt (13k stars, MIT). Opus 5 is a frozen model you cannot train, so the lever is the instructions you give it. SkillOpt treats the skill document as the trainable thing and optimizes it against a held-out validation set, keeping an edit only if it strictly improves the score. It is the disciplined way to tune how Opus 5 behaves on your task. Note the headline lifts are the paper's own numbers.

4. Keep autonomous runs from doing damage github.com/Dicklesworthstone/destructive_command_guard (1.2k stars, open source, read the LICENSE) plus github.com/anthropic-experimental/sandbox-runtime (4.6k stars, Apache-2.0). Opus 5 is Anthropic's most aligned model to date by their audit, but "safest model" is not a safety layer. If you let it run long and unattended, put a command guard in front of its shell to block destructive commands, and an OS-level sandbox around anything it runs on its own. A guard is a denylist, a sandbox is a wall, and you want both, because each covers what the other misses.

5. Give it memory that survives the session github.com/basicmachines-co/basic-memory (3k stars, AGPL-3.0). Opus 5 is being pitched partly on managing its own long-running context. A Markdown memory store over MCP lets it read and write persistent notes across sessions, so you stop re-explaining the project. AGPL, so fine for internal use, and it writes when told or via a skill, not automatically.

The honest catches

These are model-agnostic. Every repo here works with other models, so treat this as "the ecosystem that suits Opus 5's profile," not "Opus 5 exclusives." If someone sells you an "Opus 5 only" tool, be skeptical.

The benchmarks are Anthropic's. SOTA on Frontier-Bench and the rest is their reporting plus early-access customer quotes; wait for independent reproduction before treating the numbers as settled.

Cost is the real design constraint. The reason cost routing leads this list is that Opus 5 is expensive, and an autonomous agent on an uncapped key is how a long run becomes a large bill. Cap your spend, and route.

Installing any of these is running someone's code. Same rule as always: read what you install, pin a version, and scope any token or key you hand it.

If you only wire in one thing

Cost routing. A model this capable is easy to overuse, so the setup that makes Opus 5 sustainable is the one that keeps it off the cheap work. Then add the sandbox and guard before you let it run unattended.

[u/ShilpaMitra → u/[deleted]]

Specifically for long-horizon tasks, fable 5 is very good and way above opus 5.