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 Wenaixi/dsh-ponytail --skill ponytail-auditgit clone --depth 1 https://github.com/Wenaixi/dsh-ponytailWrote 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/wenaixi/dsh-ponytail/ponytail-audit)<a href="https://agentmods.dev/skills/wenaixi/dsh-ponytail/ponytail-audit"><img src="https://agentmods.dev/badge/skills/wenaixi/dsh-ponytail/ponytail-audit/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/wenaixi/dsh-ponytail/ponytail-audit"><img src="https://agentmods.dev/badge/skills/wenaixi/dsh-ponytail/ponytail-audit.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.00106 | $0.00471 |
| Opus 5 | $0.00053 | $0.00235 |
| Sonnet 5 | $0.00021 | $0.00094 |
| Haiku 4.5 | $0.00011 | $0.00047 |
Grade A, and why
ponytail-audit 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 11d 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.
What it actually says
ponytail-review 的全仓版，扫描整棵目录树而非 diff，按可删收益从大到小排序。
标签
与 ponytail-review 相同：
delete:死代码、未使用的灵活性、臆想功能。替代：无。stdlib:标准库已有的东西被手写了一遍，写出函数名。native:依赖或代码在做平台已有的事，写出平台特性名。yagni:只有一个实现的抽象、没人改的配置、只有一个调用方的分层。shrink:同样逻辑，更少行数，给出更短写法。
猎物
标准库或平台已能覆盖的依赖、只有一个实现的接口、只有一个产品的工厂、只做转发的包装、只导出一个东西的文件、僵死的开关和配置、手写的标准库。
输出
每条发现一行，按可删行数排序：<标签> <该删什么>。<替代方案>。[路径]。
结尾汇总 net: -<N> 行，-<M> 个依赖可删。 若无可删之处：已足够精简，直接发版。
边界
范围：只看过度设计和复杂度。正确性 bug、安全漏洞、性能问题明确不在范围内，请走常规评审通道。只列发现，不动手改。一次性报告。 「stop ponytail-audit / 正常模式」可退出。
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.
- 11d ago First seen · 32 lines · 106 tokens per session scan A 8e68e9a4ab19
ponytail-audit is a skill published in the GitHub repository Wenaixi/dsh-ponytail (7 stars, last pushed 20d ago), licensed MIT. It adds 106 tokens to every session and 471 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
delivery-review
Adversarial self-review before delivery. Use once the implementation reaches green and before you declare the work done — assume the delivery fails its own spec, hunt for the strongest supportable objections, answer them, and re-review after fixes.
code2skill-review-source
A read-only review skill for checking whether a Code2Skill-generated result matches the source code it was authorized to use. It examines request handling, tool handoffs, transformations, authentication, and attachments.
code-review-zh
A Git-based code review workflow that compares changes from a chosen commit, branch, tag, or merge point. It checks both whether the code follows the repository's written standards and whether it implements the requested specification.
improve-codebase-architecture-zh
A codebase architecture review that scans for modules that hide useful complexity poorly, then produces a visual HTML report and discusses one selected finding in depth.
implement-zh
An implementation workflow for completing work described in a specification or tickets. It encourages test-first development where appropriate, runs checks during the work, and ends with review and a commit.
coding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.