Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/kensaurus/cursor-kenji/burndown-full)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/burndown-full"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/burndown-full/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/burndown-full"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/burndown-full.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00563 |
| Opus 5.5 | $0.00010 | $0.00225 |
| Sonnet 5.5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
burndown-full scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 27d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Burndown Full
Drive a partially-executed plan to 100% coverage across the entire codebase. Use this when a refactor / migration / rename / rule-application was planned and started but stopped before it was actually complete everywhere.
Follow the burndown-full skill end to end. Do not improvise a shortcut version of it. In brief:
- Recover the change from the plan +
git diff/git log, and express it as a searchable MATCH pattern (still-needs-changing) and DONE pattern (already-changed). If it can't be made searchable, stop and ask. Discover the repo's typecheck/lint/test/build commands. - Enumerate the full worklist with a repo-wide
rgfor MATCH — the whole repo, not the plan's file list. Hunt the usual misses: barrels, re-exports, aliased/namespace imports, tests, stories, snapshots, fixtures, configs, type defs, docs. Write every occurrence to.cursor/burndown-state.mdand state the total count out loud (vs. how many the plan named). - Execute in batches of 5–10 files, ticking each off in
.cursor/burndown-state.mdimmediately per batch. Append any newly discovered occurrences. Do not pause to ask "continue?" — keep going until the worklist is empty. Re-read the state file instead of trusting memory if context gets long. - Prove completeness: re-run the MATCH search from scratch (expect zero hits), sweep for orphans, then whole-project typecheck + lint + test + build. Any new hit or failure → add to the worklist and loop back to step 3.
- Report coverage (call out files the plan missed), verification results, intentional exceptions, and any genuine ambiguities needing a human.
Done is defined by verification, not by effort: a from-scratch search for the old pattern returning zero and the project checking clean — never "I edited the planned files."
The plan is a hypothesis about scope, never its limit. The repo is bigger than the plan and bigger than your context window; the state file is your memory and the fresh grep is your source of truth.
The full playbook lives in the burndown-full skill.
Related: approved-plan-execution rule for approved-plan execution, plan-* skills for audit-only burndowns before changes.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 27d ago Changed · +1 lines 808c654c8609
- 1mo ago First seen · 25 lines · 25 tokens per session scan A fca713c03209
burndown-full is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 563 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
learn
Learn about Task Master capabilities through interactive exploration.
show-task
Show detailed task information with rich context and insights.
list-tasks
List tasks with intelligent argument parsing.
remove-all-subtasks
Clear all subtasks from all tasks globally.
validate-dependencies
Validate all task dependencies for issues.
smart-workflow
Execute an intelligent workflow based on current project state and recent commands.