Borrowing it
Nothing to install: this file belongs to engasnm111/lnwjud. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/engasnm111/lnwjud/main/.agents/skills/ponytail-audit/SKILL.mdgit clone --depth 1 https://github.com/engasnm111/lnwjudWrote 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/engasnm111/lnwjud/ponytail-audit)<a href="https://agentmods.dev/skills/engasnm111/lnwjud/ponytail-audit"><img src="https://agentmods.dev/badge/skills/engasnm111/lnwjud/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/engasnm111/lnwjud/ponytail-audit"><img src="https://agentmods.dev/badge/skills/engasnm111/lnwjud/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.00105 | $0.00402 |
| Opus 5 | $0.00053 | $0.00201 |
| Sonnet 5 | $0.00021 | $0.00080 |
| Haiku 4.5 | $0.00011 | $0.00040 |
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 today.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- ponytail-audit — 100% identical, 0 lines differ
- ponytail-audit — 100% identical, 0 lines differ
- ponytail-audit — 100% identical, 0 lines differ
- ponytail-audit — 100% identical, 0 lines differ
- ponytail-audit — 100% identical, 0 lines differ
- ponytail-audit — 100% identical, 0 lines differ
- ponytail-audit — 100% identical, 0 lines differ
- ponytail-audit — 98% identical, 4 lines differ
What it actually says
ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank findings biggest cut first.
Tags
Same as ponytail-review:
delete:dead code, unused flexibility, speculative feature. Replacement: nothing.stdlib:hand-rolled thing the standard library ships. Name the function.native:dependency or code doing what the platform already does. Name the feature.yagni:abstraction with one implementation, config nobody sets, layer with one caller.shrink:same logic, fewer lines. Show the shorter form.
Hunt
Deps the stdlib or platform already ships, single-implementation interfaces, factories with one product, wrappers that only delegate, files exporting one thing, dead flags and config, hand-rolled stdlib.
Output
One line per finding, ranked: <tag> <what to cut>. <replacement>. [path].
End with net: -<N> lines, -<M> deps possible. Nothing to cut: Lean already. Ship.
Boundaries
Scope: over-engineering and complexity only. Correctness bugs, security holes, and performance are explicitly out of scope. Route them to a normal review pass. Lists findings, applies nothing. One-shot. "stop ponytail-audit" or "normal mode" to revert.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 42 lines · 105 tokens per session scan A 5560b8e383db
ponytail-audit is a skill published in the GitHub repository engasnm111/lnwjud (153 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 402 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-09-11.
Other skills, from other repositories
handoff
Transfer the current coding, debugging, planning, or architecture session to AI Badger. Use for broad session continuation; use badger-review for an independent review.
badger-review
Prepare current-session guidance for an independent AI Badger review of recent repository work. Use only when the user wants a Badger review, not for generic review requests or session continuation.
open-code-review
Use Alibaba Open Code Review (ocr) to review git diffs, staged changes, branches, or scan a workspace, then summarize findings and optionally fix high-confidence issues.
Release Readiness
Review a change against release gates, rollback safety, validation evidence, and operational risk.
review
L1 internal review with auto-detection, design comparison, and Gate escalation path.
sop-review
A structured code-review procedure for checking a task against project rules and acceptance criteria. It loads the task, relevant standards, and the Git changes before reviewing every required checkpoint.