ken-debt SKILL.md skillA
ken-debt from rajnandan1/ken is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rajnandan1/ken/ken-debt@git:20260826.e88374fPins git:20260826.e88374f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rajnandan1/ken
- Path
.openclaw/skills/ken-debt/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260826.e88374f, committed Aug 26, 2026
- First version recorded
- Aug 26, 2026
- Size
- 1,453 bytes
- Repository stars
- 14
- License
- a license file GitHub does not identify
Harvest every ken: ceiling comment into one ledger, so brute-force deferrals get tracked instead of forgotten. One-shot report.
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 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@sha256:8b792b1e48e02006The line at the top of this page pins the label git:20260826.e88374f, 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_c33fgysxpn3gshjq)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.e88374f latest | 2026-08-26 | e88374f | 1,453 B | A | view · diff |
| git:20260826.fb9074e | 2026-08-26 | fb9074e | 1,461 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 (1453 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 · 14 stars · license a license file GitHub does not identify · pushed 2026-10-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c33fgysxpn3gshjq GET https://markdownregistry.com/api/v1/resolve?ref=rajnandan1/ken/ken-debt GET https://markdownregistry.com/api/v1/blob/8b792b1e48e020069a7e9ee930c9ac6f3d15d99fa18779febecd6a1e266fad1f
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.