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.
npx skills add kensaurus/cursor-kenji --skill complete-everythinggit 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/skills/kensaurus/cursor-kenji/complete-everything)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/complete-everything"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/complete-everything/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/skills/kensaurus/cursor-kenji/complete-everything"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/complete-everything.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 86 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00057 | $0.03236 |
| Opus 5.5 | $0.00023 | $0.01294 |
| Sonnet 5.5 | $0.00011 | $0.00647 |
| Haiku 4.5 | $0.00006 | $0.00324 |
Grade A, and why
complete-everything 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 23d 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.
How it starts
The opening of the file, as written. The whole thing — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Everything
Degree of freedom: MIXED. Relevance of parked items [HIGH freedom];
state-file ticks, verification ladder, and completion-judge
[LOW freedom — run exactly].
How to reason
- Observe — plan items, parked quotes, git diff, baseline failures
- Interpret — connected to the approved goal vs explicit non-goal
- Classify — plan / previously-parked / discovered / human-gate
- Severity — an unchecked acceptance criterion blocks the report
Worked example
Observe: plan shipped the UI; "out of scope" noted the RLS migration file; live API 404s. Interpret: the parked migration is connected — the UI cannot work without it. Classify: previously-parked now in scope; deploy+verify the RPC. Done: state file ticked with evidence; completion-judge PASS.
Self-critique before reporting
- Evidence — every tick cites a fresh command/result
- No deferral language — connected parked work was closed, not restated
- Judge —
completion-judgeran; CONTINUE loops back - Right owner — one mechanical pattern →
burndown-full; dirty-tree PR →workflow-release-prep
Completion contract
Drive the approved outcome through implementation, repair, and verification in one continuous run. Do not stop at phase boundaries or ask whether to continue. Do not claim success from memory, compilation alone, or the original plan's checkboxes.
The closure set contains:
- every unfinished or partially finished plan item;
- every
out of scope, follow-up, optional, nice-to-have, or future-work item parked by the plan or prior completion report that is materially connected to the approved goal; - every defect, missing test, contract mismatch, or regression discovered in the affected blast radius;
- every failure introduced by the work or blocking proof of the outcome.
This is not permission for unrelated repository-wide cleanup. Do not silently reopen explicit user non-goals, rejected features, or unrelated pre-existing debt. Record those as baseline context, not closure items. If relevance is unclear, decide from the approved user outcome; ask only when the answer would materially change product behavior.
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.
- 23d ago Changed · +3 lines d413d786e0f2
- 29d ago Changed · +3 lines · -10 tokens per session 2bbc0458e11e
- 1mo ago First seen · 290 lines · 67 tokens per session scan A 079c8f88fede
complete-everything is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 24d ago), licensed MIT. It adds 57 tokens to every session and 3,236 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
noteplan
Read, search, create, and edit NotePlan notes and daily logs directly via the filesystem. Use this skill whenever the user references NotePlan, daily notes, weekly notes, project notes, or wants to check/update their planning. Triggers: 'noteplan', 'daily note', 'today's note', 'weekly note', 'check my notes', 'add to…
lno-task-prioritization
Classify tasks as Leverage, Neutral, or Overhead using Shreyas Doshi's LNO framework to maximize impact and reduce stress. Use when the user is planning their week, feeling overwhelmed, prioritizing a to-do list, doing sprint planning, or asking how to spend their time more effectively.
dynamic-context
Use when managing context window to optimize token usage and prevent context bloat.
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
agent-work-receipt
Produces a conservative agent work receipt after completed work: finished output, time estimates, review burden, risks, and value judgment. Use when the user invokes /agent-work-receipt, asks for a work receipt, or wants to measure agent productivity honestly after a session.
hot-reload-optimizer
Optimizes hot module replacement and fast refresh for development speed with Vite, Next.js, and webpack configurations. Use when users request "hot reload", "HMR optimization", "fast refresh", "dev server speed", or "development performance".