ponytail-gain — Claude Code skill: what it does, how to install
Displays measured benchmark savings across code volume, token spend, and execution time for Ponytail. Useful when evaluating the toolset.
npx skills add DietrichGebert/ponytail --skill ponytail-gain -a claude-codeWhat ponytail-gain does
The skill renders an ASCII scoreboard showing published benchmark data from Ponytail 5. The figures come from running headless Claude Code with Opus 5.5 across 39 tasks with 5 runs each, covering FastAPI and React features, bug fixes, and security tickets. Against the unassisted baseline, lines of code dropped by 53%, output tokens by 45%, cost by 26%, and time by 41%.
Execution is strictly one-shot. It writes no files, sets no flags, and never claims to calculate savings for your current repository. Because an alternative baseline does not exist in an active project, it avoids fabricated stats and points to /ponytail-debt instead.
Install this if you want quick reference data on Ponytail before applying it across projects. Skip it if you expect dynamic telemetry on your current workspace.
What it helps with
- check Ponytail benchmark metrics for token and cost savings
- review baseline comparisons across 39 sample agent tasks
- verify test pass rates under Claude Code Opus 5.5 runs
- find references to live debt and audit commands
Example prompts for the agent
- /ponytail-gain
- what does ponytail save
- ponytail impact
How to install ponytail-gain
1Skills CLI (Vercel)
npx skills add DietrichGebert/ponytail --skill ponytail-gain -a claude-code2Manually: put the files in place
~/.claude/skills/ponytail-gain/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ponytail-gain/
1Skills CLI (Vercel)
npx skills add DietrichGebert/ponytail --skill ponytail-gain -a codex2Manually: put the files in place
.agents/skills/ponytail-gain/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add DietrichGebert/ponytail --skill ponytail-gain -a cursor2Manually: put the files in place
.cursor/skills/ponytail-gain/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install DietrichGebert/ponytail ponytail-gain2Manually: put the files in place
.github/skills/ponytail-gain/SKILL.md1Skills CLI (Vercel)
npx skills add DietrichGebert/ponytail --skill ponytail-gain -a gemini-cli2Platform CLI
gemini skills install https://github.com/DietrichGebert/ponytail --path skills/ponytail-gainManually: put the files in place
.devin/skills/ponytail-gain/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add DietrichGebert/ponytail --skill ponytail-gain -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set6
The whole set →Similar
Questions about ponytail-gain
How do I install ponytail-gain in Claude Code?
Run npx skills add DietrichGebert/ponytail --skill ponytail-gain -a claude-code in your terminal. You can also save the file directly to ~/.claude/skills/ponytail-gain/SKILL.md.
What does ponytail-gain do?
It outputs an ASCII scoreboard summarizing benchmark savings in lines of code, tokens, and cost. It acts as a one-shot reference display without altering your code.
Does ponytail-gain measure savings in my current repo?
No, it displays fixed benchmark averages from 39 test cases. For repo-specific tracking of deferred shortcuts, run /ponytail-debt.
Source text
SKILL.md · MIT
---
name: ponytail-gain
description: >
Show ponytail's measured savings (code, cost, speed) from the benchmark.
One-shot display. Use for /ponytail-gain, "what does ponytail save",
"ponytail impact".
---
# Ponytail Gain
Display this scoreboard when invoked. One-shot: do NOT change mode, write flag
files, or persist anything.
The figures are the published agentic benchmark of Ponytail 5: headless Claude
Code (Opus 5.5, default effort) on 39 tasks (feature tickets in a real FastAPI +
React repo, bug fixes, security and privacy cases, small apps), 5 runs each,
against the same agent without the skill. 18 of the tasks have hidden checks
for correctness and safety. Each figure is the geometric mean of the per-task
medians. They are measured, not computed from the current repo.
Source: `benchmarks/results/2026-10-07-agentic.md` and the README.
## Scoreboard
Render plain ASCII bars. The bar length shows ponytail as a share of the
no-skill baseline; the label carries the exact figure:
```
ponytail gain benchmark · 39 tasks × 5 runs · Opus 5.5
no-skill ████████████████████ 100%
Lines of code █████████··········· 47% ▼ 53%
Output tokens ███████████········· 55% ▼ 45%
Cost ███████████████····· 74% ▼ 26%
Time ████████████········ 59% ▼ 41%
Hidden checks passed 97% (no-skill 96%)
Tests where the logic needs one 98% (no-skill 68%)
This repo: /ponytail-debt (shortcuts you deferred)
/ponytail-audit (what's still cuttable)
```
## Honesty boundary
These are benchmark averages, not this repo. NEVER print a per-repo savings
number ("you saved X lines/tokens here"): the unbuilt version was never
written, so there is no real baseline to subtract from in a live repo. The
only real per-repo figures come from `/ponytail-debt` (a counted ledger), and
this card points there instead of inventing one.
## Boundaries
One-shot display. Edits nothing, changes no mode.
© DietrichGebert · MIT · DietrichGebert/ponytail