burndown-full SKILL.md skillA
burndown-full from kensaurus/cursor-kenji is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/cursor-kenji/burndown-full@git:20260929.59140daPins git:20260929.59140da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/cursor-kenji
- Path
skills/burndown-full/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260929.59140da, committed Sep 29, 2026
- First version recorded
- Aug 20, 2026
- Size
- 12,592 bytes
- Repository stars
- 9
- License
- MIT
Drive a planned mechanical change to 100% repo coverage after a run stopped early. Use when "finish the burndown", "it stopped halfway", "apply this everywhere", or "half-migrated". One plan plus deferrals → complete-everything.
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
# Burndown Full **Degree of freedom: MIXED.** Signature and batch sizing `[HIGH freedom]`; from-scratch re-search and the zero-hit gate `[LOW freedom — run exactly]`. ## How to reason 1. **Observe** — the old pattern's remaining hits from a fresh search 2. **Interpret** — planned files vs the real blast radius (tests, barrels, stories) 3. **Classify** — still-old / already-new / false-positive 4. **Severity** — leftover production call sites outrank a comment in CHANGELOG ## Worked example > **Observe:** plan listed 8 files; fresh `rg Button2` finds 14 (plus a story and a re-export). > **Interpret:** the plan was a hypothesis; barrels were missed. > **Classify:** 6 extra call sites still-old; CHANGELOG mention is false-positive. > **Done:** re-search → 0 real hits; typecheck/lint/tests green. ## Self-critique before reporting - **Fresh search** — done is zero hits from scratch, not memory - **Plan is not the boundary** — extras were appended, not ignored - **No skip** — tests/stories/re-exports burned down too - **Right owner** — one approved plan + deferrals → `complete-everything`; inventory → `housekeep-backlog` ## What problem this solves …
Read the whole file at its exact version.
How to install
mdr add kensaurus/cursor-kenji/burndown-full@sha256:f089e395ff8cf016The line at the top of this page pins the label git:20260929.59140da, 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_rw7mhb2ywrsh5poc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 20, 2026 and Sep 29, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260929.59140da latest | 2026-09-29 | 59140da | 12,592 B | A | view · diff |
| git:20260923.68c095e | 2026-09-23 | 68c095e | 12,679 B | A | view · diff |
| git:20260923.cf348bd | 2026-09-23 | cf348bd | 12,711 B | A | view · diff |
| git:20260821.2a41031 | 2026-08-21 | 2a41031 | 12,566 B | A | view · diff |
| git:20260820.950107c | 2026-08-20 | 950107c | 11,418 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 (12592 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
kensaurus/cursor-kenji · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rw7mhb2ywrsh5poc GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/cursor-kenji/burndown-full GET https://markdownregistry.com/api/v1/blob/f089e395ff8cf0168a6f77f6af07b3b1a2ba8c74483aa47ba1fc39ef2f583b78
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.
More from kensaurus/cursor-kenji
Every file in kensaurus/cursor-kenji