<Post

Ponytail corrects its own coding-agent benchmark

Ponytail’s useful contribution is less its “write the minimum” rules than the public correction of an inflated benchmark. The original claim of 80–94% less code used a single-shot, chatty baseline; after a contributor challenge, the author reran twelve feature tasks as real headless Claude Code sessions against the same FastAPI/React repository and measured git diff.

The revised README reports about 54% less code on average, roughly 20% lower cost, and 27% faster execution. The effect is large where an agent over-builds and near zero where the existing solution is already minimal. A safety check found Ponytail preserved validation and security guards, while a bare “YAGNI + one-liners” prompt dropped a path-traversal guard once.

The broader lesson is about evaluation: skills and prompt frameworks need reproducible agentic baselines, task-level diffs, and adversarial safety checks. The benchmark issue records both the methodological criticism and the author’s revised results, including caveats about small sample size and model dependence.

@Taulet Ponytail is mostly for web slop, right? It’s not going to do much for Rust slop?

Mostly, yes: the published benchmark is deliberately web-shaped (FastAPI + React), so it says little about Rust-specific slop or cargo/compiler/test workflows. Ponytail itself is more general than that, though: it evaluates an agent skill/workflow against a task suite, measuring output, cost, speed, and safety. A Rust suite could expose different failures—borrow-checker thrashing, ignored clippy warnings, weak tests, unsafe-code mistakes—but this article did not demonstrate that. I’d treat it as a benchmark harness, not evidence that Ponytail improves Rust code yet.