Borrowing it
Nothing to install: this file belongs to ouranos-labs/pseolint. 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/ouranos-labs/pseolint/main/.claude/skills/ponytail-debt/SKILL.mdgit clone --depth 1 https://github.com/ouranos-labs/pseolintWrote 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/ouranos-labs/pseolint/ponytail-debt)<a href="https://agentmods.dev/skills/ouranos-labs/pseolint/ponytail-debt"><img src="https://agentmods.dev/badge/skills/ouranos-labs/pseolint/ponytail-debt/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/ouranos-labs/pseolint/ponytail-debt"><img src="https://agentmods.dev/badge/skills/ouranos-labs/pseolint/ponytail-debt.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.00099 | $0.00440 |
| Opus 5 | $0.00049 | $0.00220 |
| Sonnet 5 | $0.00020 | $0.00088 |
| Haiku 4.5 | $0.00010 | $0.00044 |
Grade A, and why
ponytail-debt 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.
This is a copy
100% identical to ponytail-debt — 0 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.
What it actually says
Every deliberate ponytail shortcut is marked with a ponytail: comment naming
its ceiling and upgrade path. This collects them into one ledger so a deferral
can't quietly become permanent.
Scan
Grep the repo for comment markers, skipping node_modules, .git, and build
output:
grep -rnE '(#|//) ?ponytail:' . (add other comment prefixes if your stack uses them)
Each hit is one ledger row. The comment prefix keeps prose that merely mentions the convention out of the ledger.
Output
One row per marker, grouped by file:
<file>:<line>, <what was simplified>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.
The convention is ponytail: <ceiling>, <upgrade path>, so pull the ceiling
and the trigger straight from the comment. Want an owner per row too? add
git blame -L<line>,<line>.
Flag the rot risk: any ponytail: comment that names no upgrade path or
trigger gets a no-trigger tag, those are the ones that silently rot.
End with <N> markers, <M> with no trigger. Nothing found: No ponytail: debt. Clean ledger.
Boundaries
Reads and reports only, changes nothing. To persist it, ask and it writes the
ledger to a file (e.g. PONYTAIL-DEBT.md). One-shot. "stop ponytail-debt" or
"normal mode" to revert.
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 · 45 lines · 99 tokens per session scan A c84fba75f0ca
ponytail-debt is a skill published in the GitHub repository ouranos-labs/pseolint (6 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 440 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ponytail-debt, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
portaljs-check-data-quality
Audit a local or remote tabular file (CSV/TSV) for common data quality issues — schema, nulls, types, duplicates. Read-only. Use when a dataset needs a quality check before publishing, or a showcase renders wrong (blank cells, garbled numbers, an unsortable date column) and the cause needs isolating.
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
audit-website
Audit a website with the squirrelscan CLI and fix the findings in code. Runs SEO, performance, security, technical, content, accessibility, and 15 other rule categories (260+ rules), returns an LLM-optimized report, then drives an iterative fix loop, mapping issues to source files, applying fixes, and re-auditing…
suiko
A Japanese writing and review workflow for checking whether text sounds uniform, translated, unnatural, or difficult to read. It supports writing and editing documents such as reports, guides, meeting notes, proposals, and emails.
updater
Check Claude Code changelog for lintable changes and implement cclint updates. Use when a new Claude Code version ships, when CLAUDE.md claudecodelastupdated is stale, or for version gap detection, domain classification, and parallel agent dispatch across CUE schemas, hook events, known tools, and lint rules.
schliff
Deterministic linter and scorer for instruction files — SKILL.md, AGENTS.md, CLAUDE.md. No model in the loop: the same bytes score the same everywhere. Use for linting, scoring, auditing or CI-gating an instruction file, and for checking whether the commands a file promises actually resolve in the repo. Trigger…