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 dmae97/omk --skill ponytail-auditgit clone --depth 1 https://github.com/dmae97/omkWrote 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/dmae97/omk/ponytail-audit)<a href="https://agentmods.dev/skills/dmae97/omk/ponytail-audit"><img src="https://agentmods.dev/badge/skills/dmae97/omk/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/dmae97/omk/ponytail-audit"><img src="https://agentmods.dev/badge/skills/dmae97/omk/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.00977 |
| Opus 5.5 | $0.00042 | $0.00391 |
| Sonnet 5.5 | $0.00021 | $0.00195 |
| Haiku 4.5 | $0.00011 | $0.00098 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
OMK Vendoring Notice
This skill is vendored from the upstream Ponytail
project (npm: @dietrichgebert/ponytail) as a pure markdown OMK skill, copied unmodified in
substance from skills/ponytail-audit/SKILL.md at pinned commit
40e50d9
(full SHA 40e50d9e03242aa5dd53ac771950f9127362b25f).
- License: MIT. Copyright (c) 2026 DietrichGebert. Full text:
../ponytail/LICENSE(this repo's vendored copy, kept alongside the primaryponytailskill) and the upstreamLICENSEfile at the pinned commit. - Scope: only the six
skills/*/SKILL.mdfiles were vendored. Upstream's Node/Python extension code (pi-extension/,hooks/*.js,ponytail-mcp/), the Hermes Agent plugin (__init__.py,plugin.yaml), command/hook manifests, and marketplace/CI tooling are not included in OMK. Nothing in this skill executes code; it is inert markdown loaded into the system prompt. - Invocation in OMK: use
/skill:ponytail-auditor!skill:ponytail-audit(shorthand!ponytail-auditalso works when unambiguous), perpackages/coding-agent/docs/skills.md. The bare/ponytail-auditslash form referenced above describes the upstream multi-host package's own command surface (Claude Code, Codex, OpenCode, etc.) and is not an OMK command. - Updates: this is a static vendored copy, not a live package install. To pick up upstream changes, re-vendor against a newer pinned commit; there is no auto-update mechanism here.
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 · 74 lines · 105 tokens per session scan A 1c336e3f5e38
ponytail-audit is a skill published in the GitHub repository dmae97/omk (148 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 977 once invoked, about $0.0004 per session on Opus 5.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-30.
Other skills, from other repositories
review-harness
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
review
Review checkpoints in SyncPoint — create review requests, add checklists, submit evidence, approve or request changes. Use when reviewing another agent's work before it can proceed.
pr-review
Review Cool Workflow pull requests or branch diffs. Use when Codex must inspect code changes for bugs, regressions, FreeBSD/POLA violations, missing tests, generated artifact drift, release-contract risk, or CI implications, and return findings first with file/line citations.
gh-compile-issues
Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…