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.
npx skills add sampleXbro/agentsmesh --skill ponytail-helpgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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.
[](https://agentmods.dev/skills/samplexbro/agentsmesh/ponytail-help)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/ponytail-help"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/ponytail-help/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.
<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/ponytail-help"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/ponytail-help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.00731 |
| Opus 5.5 | $0.00022 | $0.00292 |
| Sonnet 5.5 | $0.00011 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
ponytail-help 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 1mo 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.
This is a copy
91% identical to ponytail-help — 32 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ponytail Help
Display this reference card when invoked. One-shot, do NOT change mode, write flag files, or persist anything.
Levels
| Level | Trigger | What change |
|---|---|---|
| Lite | /ponytail lite |
Build what's asked, name the lazier alternative in one line. |
| Full | /ponytail |
The ladder enforced: YAGNI → stdlib → native → one line → minimum. Default. |
| Ultra | /ponytail ultra |
YAGNI extremist. Deletion before addition. Challenges requirements before building. |
Level sticks until changed or session end.
Skills
| Skill | Trigger | What it does |
|---|---|---|
| ponytail | /ponytail |
Lazy mode itself. Simplest solution that works. |
| ponytail-review | /ponytail-review |
Over-engineering review: L42: yagni: factory, one product. Inline. |
| ponytail-audit | /ponytail-audit |
Whole-repo over-engineering audit: ranked list of what to delete. |
| ponytail-debt | /ponytail-debt |
Harvest ponytail: shortcut comments into a tracked ledger. |
| ponytail-gain | /ponytail-gain |
Measured-impact scoreboard: less code, less cost, more speed. |
| ponytail-help | /ponytail-help |
This card. |
Codex uses @ponytail, @ponytail-review, and @ponytail-help; Claude Code
and OpenCode use the slash-command forms above (OpenCode ships all six as
slash commands).
Deactivate
Say "stop ponytail" or "normal mode". Resume anytime with /ponytail.
/ponytail off also works.
Configure Default Mode
Default mode = full, auto-active every session. Change it:
Environment variable (highest priority):
export PONYTAIL_DEFAULT_MODE=ultra
Config file (~/.config/ponytail/config.json, Windows: %APPDATA%\ponytail\config.json):
{ "defaultMode": "lite" }
Set "off" to disable auto-activation on session start, activate manually
with /ponytail when wanted.
Resolution: env var > config file > full.
Update
Enable auto-update once: open /plugin, go to Marketplaces, pick ponytail, Enable auto-update. Claude Code then pulls new versions at startup (run /reload-plugins when it prompts). Manual refresh: /plugin marketplace update ponytail then /reload-plugins.
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.
- 1mo ago First seen · 69 lines · 56 tokens per session scan A c9623c5f8027
ponytail-help is a skill published in the GitHub repository sampleXbro/agentsmesh (26 stars, last pushed 29d ago), licensed MIT. It adds 56 tokens to every session and 731 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to ponytail-help, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
tournament-manager
Tournament manager for the EasyChamp platform. Use when the user wants to create or operate a sports league, tournament, or bracket — covers generating a league, spinning up a tournament under it, building the bracket, producing a schedule with venues, and entering match results. Activates for 'create a league'…
replay
Find, analyze, and share AI coding sessions with vibe-replay. Use when the user asks for a replay, wants to find a past session, run a session retro, share Cursor/Claude/Codex session context, or attach session context to a PR.
schedules
GTM Agent schedules — recurring prompts the GTM Agent runs on a cadence, each occurrence starting a fresh agent task. Use for any request to do something on a schedule or recurring cadence: a daily digest, a weekly report, checking or changing when a scheduled run happens next, pausing or deleting one.
routines
Clay routines — create a routine from an existing function/workflow, then run a saved routine that exists in this workspace. Use when the user asks to create/register a routine, or to run, execute, or trigger a function, workflow, or routine (by name or id), pass it inputs, or check the results/status of a run. For…
credits-quotas-plans
Use when the user asks about credits, quotas, or plan limits, or verified usage requires a significant-spend warning or reveals a limit. Covers data-credit balance, action-execution balance, search result caps, period quotas, and upgrade paths before starting work that would only partially complete.