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/commit)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/commit"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/commit/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/commit"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/commit.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.00013 | $0.00151 |
| Opus 5.5 | $0.00005 | $0.00060 |
| Sonnet 5.5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
commit 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 22d 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
/commit
Create one conventional commit from an already-scoped change. Never push.
This command is a thin entry point. The full deliberate-staging and
message-writing playbook lives in workflow-git-commit.
Use /commit when the files or hunks are already scoped and you need one
commit. It does not widen staging, push, or open a PR.
Related: workflow-release-prep for a whole dirty tree through merge-ready
PR; workflow-pr for an already-committed branch or open PR.
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.
- 22d ago Changed · +1 lines 4cca04239981
- 1mo ago First seen · 18 lines · 13 tokens per session scan A 56923dd70ed6
commit is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 17d ago), licensed MIT. It adds 13 tokens to every session and 151 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
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.