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/update-deps)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/update-deps"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/update-deps/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/update-deps"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/update-deps.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.00019 | $0.00295 |
| Opus 5.5 | $0.00008 | $0.00118 |
| Sonnet 5.5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
update-deps 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 1mo 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
/update-deps
Audit outdated dependencies, research breaking changes, update one at a time, verify each, commit separately.
This command is a thin entry point. The full playbook lives in the workflow-housekeep skill (Phase 3 — Dependency Updates), which auto-detects package manager (npm/pnpm/yarn/bun/pip/poetry/cargo/go) and classifies updates by risk (patch/minor/major/security).
Use /update-deps when you want to explicitly trigger dependency review. Otherwise, say "update deps", "fix vulnerabilities", or "what's outdated" and the skill auto-fires.
Next.js: check the current support line and end-of-life before choosing a
target (npm view next dist-tags, https://endoflife.date/nextjs); do not assume
a version from memory. Ask: "is there a Next.js security release this month?"
and prefer npx @next/codemod@canary upgrade latest over a blind major bump.
next lint was removed in Next 16 — call ESLint directly.
Related: audit-security for vulnerability triage, workflow-git-commit for the commit-per-update pattern.
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.
- 1mo ago Changed · +1 lines 995822191351
- 1mo ago Changed · +1 lines 3dfbbb3cebc4
- 1mo ago First seen · 20 lines · 19 tokens per session scan A 2ff83e364445
update-deps is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 19 tokens to every session and 295 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-09-03.
Other commands, from other repositories
commit-msg
Cursor tooling: skills, rules, subagents.
commit
Git commit with conventional commits format.
commit-changes-main
Commit directly on main/master when explicitly allowed.
commit-same-branch
Commit on the current branch with conventional message.
commit
Commit on a new branch with conventional message.
clean
Repository hygiene — clean temp files, organize execution folders.