ken-debt skillA
ken-debt is agent-read markdown (skill) from rajnandan1/ken: Harvest every `ken:` comment in the codebase into a ceilings ledger, so the deliberate brute-force ceilings ken leaves behind get tracked instead of rotting into "later means never". Use when the user says "ken debt", "/ken-debt", "what did ken defer", "list the ceilings", "ken ledger", or "what brute force did we mark". One-shot report, changes nothing..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
Every deliberate ken brute-force ceiling is marked with a `ken:` comment naming its ceiling and upgrade trigger. This collects them into one ledger so a deferral can't become permanent without notice. ## Scan Grep the repo for comment markers, skipping `node_modules`, `.git`, and build output: `grep -rnE '(#|//) ?ken:' .` (add other comment prefixes if your stack uses them) Each hit is one ledger row. The comment prefix keeps prose that mentions the convention out of the ledger. ## Output One row per marker, grouped by file: `<file>:<line>, <the brute-force form used>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.` The convention is `ken: <ceiling>, <upgrade trigger>`, 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 `ken:` comment that names no upgrade trigger gets a `no-trigger` tag; those can rot without warning. End with `<N> markers, <M> with no trigger.` Nothing found: `No ken: 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 rajnandan1/ken/ken-debt@git:20260826.e88374fmdr add rajnandan1/ken/ken-debt@sha256:36d44c9e165809e6Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_uxnpw4rt5l2hrldz)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.e88374f latest | 2026-08-26 | e88374f | 1,645 B | A | view · diff |
| git:20260826.fb9074e | 2026-08-26 | fb9074e | 1,643 B | A | view |
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 (1645 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
rajnandan1/ken · 10 stars · license NOASSERTION · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uxnpw4rt5l2hrldz GET https://markdownregistry.com/api/v1/resolve?ref=rajnandan1/ken/ken-debt GET https://markdownregistry.com/api/v1/blob/36d44c9e165809e60f67fe326a169a1239ec89dc4362e0788e6379e4773bbf1f
Your agent 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.