Borrowing it
Nothing to install: this file belongs to dradoaica/cogov-a-sdlc. 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/dradoaica/cogov-a-sdlc/main/.agents/skills/ponytail-audit/SKILL.mdgit clone --depth 1 https://github.com/dradoaica/cogov-a-sdlcWrote 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/dradoaica/cogov-a-sdlc/ponytail-audit)<a href="https://agentmods.dev/skills/dradoaica/cogov-a-sdlc/ponytail-audit"><img src="https://agentmods.dev/badge/skills/dradoaica/cogov-a-sdlc/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/dradoaica/cogov-a-sdlc/ponytail-audit"><img src="https://agentmods.dev/badge/skills/dradoaica/cogov-a-sdlc/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.00089 | $0.00835 |
| Opus 5.5 | $0.00036 | $0.00334 |
| Sonnet 5.5 | $0.00018 | $0.00167 |
| Haiku 4.5 | $0.00009 | $0.00084 |
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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Ponytail Audit (Repository-Wide Quality & Bloat Audit)
Purpose
Conducts a comprehensive, read-only quality and maintainability audit across the entire codebase or specified subsystem. Identifies dormant bugs, security vulnerabilities, scalability limits, missing tests, and architectural bloat.
Inputs required
- Target scope: specific directory, module, or entire repository.
- System entry points, architecture docs (
docs/adrs/), dependency lists, and test suites.
Preconditions / governance gates
- Read-Only Inspection: Generates an informational report; does not modify code or configuration.
- Traceability: References existing architecture documents when identifying structural deviations.
Procedure (mandatory)
- Map system architecture & entry points:
- Read system manifests (README, build configs, dependencies, package files).
- Identify primary entry points (routes, controllers, background jobs, CLIs).
- Determine baseline operational scale from deployment and configuration files.
- Map critical data flows (user input, authentication, persistence, cross-process communication).
- Scan for defects and complexity:
- Bugs & Inconsistencies: Inconsistent rule applications, unhandled edge cases, broken assumptions.
- Security & Data Safety: Missing input sanitization, insecure defaults, unmanaged secrets, uncommitted transactions.
- Scalability & Concurrency: Race conditions, unbounded memory structures, N+1 query patterns.
- Untested Risk: High-consequence logic lacking automated regression coverage.
- YAGNI & Bloat: Dead modules, unused config flags, single-implementation interfaces, external dependencies replaceable by standard libraries.
- Verify and rank findings:
- Ensure every reported item includes a concrete problem scenario and minimal fix.
- Respect annotated shortcuts only if they carry a
track:reference (# shortcut: <limit>, <trigger> (risk: ..., track: <US-…|PRB-…>)) and current system requirements do not exceed their limit. Report shortcuts withouttrack:asShould fix(undocumented debt). - Rank findings by severity:
Must fix,Should fix,Nice to have(capped at 20 most impactful findings).
- Render a structured audit report:
- What this repo does: 2–3 sentences defining core functionality and assumed load.
- Grouped Findings: 4-part details (What this is, Problem, Fix, If we skip it).
- Verdict: Overall health summary.
- Lean Opportunity:
Lean: -<N> lines, -<M> dependencies possible. - Coverage Disclosure: Explicitly list paths/modules that were not inspected.
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.
- 8d ago First seen · 76 lines · 89 tokens per session scan A 321deeafb42a
ponytail-audit is a skill published in the GitHub repository dradoaica/cogov-a-sdlc (3 stars, last pushed 5d ago), licensed MIT. It adds 89 tokens to every session and 835 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-10-18.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.