用 Jev 做路由把 Opus 工作流成本压到 1/20

Branko Trcek @Brankotrcek原推发布于 2026.10.13

在 X 上打开原推

THIS IS PURE F*CKING GOLD an ex-Anthropic engineer just leaked a confidential prompt for making Opus 5.5 workflows 20x cheaper. the trick: Jev decides which tasks actually reach the expensive model finished jobs return their saved results. routine decisions go through Jev. Opus gets the evidence and instructions for work that needs deeper analysis give each component a specific job: → code checks duplicates, input changes, and completed work → Jev selects execute, skip, or human review → Opus investigates selected tasks and produces the result → checks decide whether to accept it or request one correction the budget killer is letting an agent retry without explaining what failed. it reads the same context, repeats the same reasoning, and charges you again attach the failed requirement and relevant evidence to the revision. keep unresolved work visible for review every completed task has to show: → what was requested → which route Jev selected and why → whether the result passed its checks → the total cost, including retries and manual fixes the example covered 240 jobs across 8 recurring workflows. only 12 needed an Opus investigation after repeat checks and routing give your coding agent one recurring task, then ask: “build a workflow where code catches repeated work, Jev selects the next action, and Opus handles the tasks that need investigation” 1. define the inputs, available actions, and what counts as a useful result. ask for missing information before building 2. connect Jev and log each routing decision. give Opus only the context needed for the selected task 3. check the output and allow one targeted correction. save the result with its input version 4. run in shadow mode first. compare the proposed routes with actual outcomes before enabling execution start with one workflow and track cost per accepted result the article below gives you the full Jev + Opus 5.5 setup, prompts, and cost breakdown to build a 20x more efficient workflow ↓

这条是引用着另一条写的：x.com/0xnineinch/status/2108604801411879139