I'm not sure that it needs to be this complicated. But yes, I am interested in the problem of hard guardrails between multiple agents, and it is not an easy problem to solve.
The answer to that is no. A lot of these are released on vibes and showing that it does what it says it does. For most organizations that care about processes and procedures thats... enough? I've worked on agentic development in enterprise and they just want their way to stamp their old methods on to the new agentic world so it can pass through their release hoops.
I've tried to benchmark them the most common public skills including those for ADLC (ie SuperPowers) couple of times here https://orcabot.com/benchmarks/agent-skills. Annoyingly I haven't been able to release one in a while because its been next to impossible to stop the new frontier models from cheating one way or another.
> 14 agents: 11 domain experts, 2 reviewers, and an adaptive composer
wow, that's a lot of domain experts, I'm convinced
Staying well behind the frontier, just in case.
I check every benchmark site weekly, compare harnesses and models, and its still pretty much just vibes
I've tried to benchmark them the most common public skills including those for ADLC (ie SuperPowers) couple of times here https://orcabot.com/benchmarks/agent-skills. Annoyingly I haven't been able to release one in a while because its been next to impossible to stop the new frontier models from cheating one way or another.
Evals showed that speed and token use improved when it was removed.....
The models have improved and internalized some of these principles.
They still have value, IMO, because they help improve consistency (at the expense of speed and cost).
My assessment has been just use the native harness.