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.svg" alt="Measured on agentmods" 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.00067 | $0.02948 |
| Opus 5 | $0.00034 | $0.01474 |
| Sonnet 5 | $0.00013 | $0.00590 |
| Haiku 4.5 | $0.00007 | $0.00295 |
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 4d 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 — 290 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
Mission (verbatim)
fix and test thoroughly on all the plan - do not defer anything. make sure proper full test is done after enhancement - also fix all out of scope.
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.
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.
- 4d 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 10d ago), licensed MIT. It adds 67 tokens to every session and 2,948 once invoked, about $0.0003 per session on Opus 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
linkedin-job-scraper
Scrapes LinkedIn job postings using the JobSpy library (python-jobspy). Use this skill whenever the user wants to find jobs on LinkedIn, search for open roles, pull job listings, build a job pipeline, source job targets for GTM research, or monitor hiring signals. Even if the user just says "find me some jobs" or…
job-search
Search for jobs matching your skills, experience, and preferences.
send-sms-textbelt
Send SMS text messages to phone numbers. Use when the user asks to send a text, send an SMS, text someone, message a phone number, or send a notification via text message.
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.
042-planning-openspec
Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization. Triggers include Create OpenSpec from an…
043-planning-github-issues
Use when you need GitHub CLI (gh) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for…