ponytail-debt SKILL.md skillA
ponytail-debt from dmae97/omk is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dmae97/omk/ponytail-debt@git:20260704.16a0c60Pins git:20260704.16a0c60 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dmae97/omk
- Path
.omk/skills/ponytail-debt/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260704.16a0c60, committed Jul 4, 2026
- Size
- 3,596 bytes
- Repository stars
- 148
- License
- MIT
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file 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 …
Read the whole file at its exact version.
How to install
mdr add dmae97/omk/ponytail-debt@sha256:106167b4adcc7bdbThe line at the top of this page pins the label git:20260704.16a0c60, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7vtlsdvzauwmg2bh)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 4, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3596 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
dmae97/omk · 148 stars · license MIT · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7vtlsdvzauwmg2bh GET https://markdownregistry.com/api/v1/resolve?ref=dmae97/omk/ponytail-debt GET https://markdownregistry.com/api/v1/blob/106167b4adcc7bdbaf6a58ce4039ce6f856de9fbced85945af40a99c4991fb91
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.