ponytail-gain

ponytail-gain is a skill for Claude Code from hyeongchankim/poneytail. It costs 34 tokens per session (456 once invoked), scanned A, a copy of ponytail-gain, MIT.

A one-time text scoreboard showing measured benchmark comparisons for Ponytail across five everyday coding tasks and three models. The figures come from published benchmark results, not from the current project.

In plain words
What is it for?
Use it to display benchmark ranges for reduced code, lower cost, and faster completion, along with the project's deferred-work and audit references.
Why use it?
It gives context about reported code, cost, and speed differences without pretending those results were measured in the current repository.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ponytail plugin — 6 skills shipped together

Good fit Use it to display benchmark ranges for reduced code, lower cost, and faster completion, along with the project's deferred-work and audit references.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hyeongchankim/poneytail/ponytail-gain
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add hyeongchankim/poneytail --skill ponytail-gain
Clone the repo
git clone --depth 1 https://github.com/hyeongchankim/poneytail

Made for: Claude Code.

Or install ponytail, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ponytail-gain

README.md
[![agentmods](https://agentmods.dev/badge/skills/hyeongchankim/poneytail/ponytail-gain/github.svg)](https://agentmods.dev/skills/hyeongchankim/poneytail/ponytail-gain)
Your own site
<a href="https://agentmods.dev/skills/hyeongchankim/poneytail/ponytail-gain"><img src="https://agentmods.dev/badge/skills/hyeongchankim/poneytail/ponytail-gain/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ponytail-gain

Your own site · 80×15
<a href="https://agentmods.dev/skills/hyeongchankim/poneytail/ponytail-gain"><img src="https://agentmods.dev/badge/skills/hyeongchankim/poneytail/ponytail-gain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 456 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00456
Opus 5 $0.00017 $0.00228
Sonnet 5 $0.00007 $0.00091
Haiku 4.5 $0.00003 $0.00046

Measured 12d ago against content hash 6268baa13052, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ponytail-gain scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to ponytail-gain — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.openclaw/skills/ponytail-gain/SKILL.md · 48 lines

What it actually says

Ponytail Gain

Display this scoreboard when invoked. One-shot: do NOT change mode, write flag files, or persist anything.

The figures are the published benchmark medians (5 everyday tasks: email validator, debounce, CSV sum, countdown timer, rate limiter; three models: Haiku, Sonnet, Opus). They are measured, not computed from the current repo. Source: benchmarks/ and the README.

Scoreboard

Render plain ASCII bars. The bar length shows the measured range; the label carries the exact figure:

  ponytail gain                     benchmark median · 5 tasks · 3 models

  Lines of code   no-skill  ████████████████████  100%
                  ponytail  ██▌·················    6–20%   ▼ 80–94%
  Cost            no-skill  ████████████████████  100%
                  ponytail  █████▌··············   23–53%  ▼ 47–77%
  Speed           ponytail  ▸ 3–6× faster

  This repo:  /ponytail-debt  (shortcuts you deferred)
              /ponytail-audit (what's still cuttable)

Honesty boundary

These are benchmark medians, 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. "stop ponytail" or "normal mode": revert.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 48 lines · 34 tokens per session scan A 6268baa13052

Subscribe to this mod's changes

ponytail-gain is a skill published in the GitHub repository hyeongchankim/poneytail (11 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 456 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ponytail-gain, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens