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 agentmods add commands/kensaurus/cursor-kenji/release-prepgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWhat 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 | $0.00022 | $0.00154 |
| Opus 5 | $0.00011 | $0.00077 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
release-prep 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 2d 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
/release-prep
Take the local working tree to a merge-ready PR against main. Do not merge.
This command is a thin entry point. The full playbook lives in the
workflow-release-prep skill.
Use /release-prep when the dirty tree (uncommitted + staged + untracked
- unpushed) should become one reviewed, merge-ready PR. Existing-PR
lifecycle stays on
/pr(workflow-pr). Product launch sweep stays onworkflow-launch-ready. Commit-message-only stays on/commit.
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.
- 2d ago First seen · 17 lines · 22 tokens per session scan A c62bf763877e
release-prep is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 154 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
Git提交和推送
Command "Git提交和推送" from nongjun/feishu-cursor-claw, covering git 提交和推送命令, 目标仓库, 操作步骤, 0. 健康检查（自动执行，有问题才输出） and 1. 检查 git 状态.
commit
Commit on a new branch with conventional message.
commit-changes-main
Commit directly on main/master when explicitly allowed.
commit-same-branch
Commit on the current branch with conventional message.
commit-msg
Cursor tooling: skills, rules, subagents.
boot
Initialize agent, verify setup, and load rules.