@BohuTANG: I used to try cross-model mutual review, but that was too slow for me. Now I've discovered a new method: /harden, which achieves great results with two rounds of convergence on the same model. Interested folks can try this skill.
Summary
BohuTANG introduces /harden, a method for same-model two-round convergence, and highlights the evot agent engine which completes complex tasks with fewer tokens and lower cost than alternatives like Claude Code.
View Cached Full Text
Cached at: 06/22/26, 05:37 AM
Evot
An agent engine that completes complex, long-running work with minimal tokens and maximum quality.
Every gain measured under a rigorous trace + eval framework — earned through relentless iteration, never guessed at.
News · Benchmark · Why · Dashboard · Install · Quickstart · Dev
Similar Articles
@BohuTANG: During the development of Evot, I discovered that to get the best out of Anthropic's Opus series models, the official Claude Code approach is basically the optimal solution, hard to bypass. After in-depth analysis and quantitative verification of the Claude Code prompt, I found that during training they already...
During the development of Evot, it was discovered that to maximize the performance of the Anthropic Opus model, the official Claude Code method is the optimal solution, because the Agent Harness behavior pattern is baked into the weights during training, rather than pure prompt engineering; in the future, Agent Harness competition will push behavior down to the model layer.
@nash_su: Microsoft released something interesting. It uses the idea of training a model to optimize skills, making adjustments to the skill's MD content each time, running the results, and if it improves, keeps pushing forward. This approach is quite interesting.
Microsoft released a new tool that uses an iterative approach similar to training models to optimize skills. It adjusts the markdown content each time, tests the results, and continuously advances improvements.
@yibie: Recommend this project. shadcn (creator of shadcn/ui) built an Agent Skill — let the most expensive model handle auditing and planning, and let the cheap model write code. The idea itself isn't new, but shadcn turned it into an installable, orchestrated system with an execution closed loop. Every design decision is practical...
shadcn released the Agent Skill project improve, which has high-cost models perform code auditing and planning while low-cost models execute, forming an installable, orchestrated system with an execution closed loop.
@interjc: Over the past few days, I used my own subagent-team skill to lead an "AI team" in development — burning through the weekly quotas of several Claude/Codex/Gemini accounts plus hundreds of dollars in API costs on a major overhaul of a monorepo project. I pulled out all the delegation records and did a retrospective:
The author shares a retrospective of using their own subagent-team skill to lead a Claude/Codex/etc. AI team through a major monorepo overhaul: cross-vendor model reviews offer the best ROI, rework volume depends on task risk rather than model tier, and they summarize a division of labor where low-tier models act as coordinators, strong models handle risky implementation, and top-tier models handle reviews.
@xiaohu: Claude Code's father's own CLAUDE.md is now just two lines... Claude Code team discusses "less is more" sharing how to communicate with models as capabilities increase: "Don't fight the model by adding more, because each generation of models gets stronger. What you painstakingly build today will soon be useless."
Claude Code team shares best practices: CLAUDE.md should be as short as possible and regularly cleared; insists on CLI over GUI because models improve too fast; using AI to fix bugs is already remarkably efficient. Core strategy: subtract, keep configuration light, and trust model capabilities.