ken-review skillA
ken-review is agent-read markdown (skill) from rajnandan1/ken: Code review for Thompson-mode violations. Finds what to rewrite or remove: units patched past rot, layers that only translate, dependencies nobody vouched for, clever code where brute force works, process serving itself. One line per finding: location, what's wrong, the move. Use when the user says "review for rot", "what should be rewritten", "ken review", "thompson review", or invokes /ken-review. Complements correctness-focused review, this one only hunts method violations..
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
Review diffs for Thompson-mode violations. One line per finding: location, what's wrong, the move. The diff's best outcome is fewer layers and a smaller trusted base. ## Format `L<line>: <tag> <what>. <the move>.`, or `<file>:L<line>: ...` for multi-file diffs. Tags: - `rot:` unit on repeated patches; the next fix is a rewrite, not patch N+1. Name the rewrite's shape. - `layer:` wrapper, adapter, or manager that adds no decision of its own. Delete it, move callers down a level. - `unvouched:` dependency or pasted code nobody present can explain. Vouch for it (read it) or replace with a few lines you own. - `fancy:` clever algorithm where the plain loop wins at this scale. Name the brute-force form; demand the measurement that justifies fancy. - `ceremony:` process, abstraction, or config that serves the process itself. Remove it. ## Examples ❌ "This caching layer might benefit from reconsidering its abstraction boundaries and perhaps simplifying the invalidation strategy." ✅ `L12-60: rot: third patch on this cache's invalidation. Rewrite on a plain dict + mtime check, ~25 lines.` …
Read the whole file at its exact version.
How to install
mdr add rajnandan1/ken/ken-review@git:20260826.e88374fmdr add rajnandan1/ken/ken-review@sha256:9eea0ce06482f862Pin 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_72yixmdfifh4vn37)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.e88374f latest | 2026-08-26 | e88374f | 2,651 B | A | view · diff |
| git:20260826.fb9074e | 2026-08-26 | fb9074e | 2,667 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 (2651 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_72yixmdfifh4vn37 GET https://markdownregistry.com/api/v1/resolve?ref=rajnandan1/ken/ken-review GET https://markdownregistry.com/api/v1/blob/9eea0ce06482f86206fd1c1a979401c451da80321f0c1c3fcafdae7d03d91100
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.