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/jaansokk/cursor_toolsWrote 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/jaansokk/cursor_tools/commit-msg)<a href="https://agentmods.dev/commands/jaansokk/cursor_tools/commit-msg"><img src="https://agentmods.dev/badge/commands/jaansokk/cursor_tools/commit-msg/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/jaansokk/cursor_tools/commit-msg"><img src="https://agentmods.dev/badge/commands/jaansokk/cursor_tools/commit-msg.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.00000 | $0.00143 |
| Opus 5.5 | $0.00000 | $0.00057 |
| Sonnet 5.5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
commit-msg 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
Write a descriptive commit message with a description
- Write a conventional commit message about the changes since the last commit in the current branch.
- Format:
type(scope): summary - Use imperative mood (e.g. "add", "fix", "update"), keep summary <= 72 chars
- 1–2 sentences on the why / impact (not a file-by-file recap)
- Add a bullet list of the changes, grouped by area if the scope is wide enough.
- Tests: if tests were run, list. If no coverage or N/A, omit this.
- Give the message as a MD snippet in chat, do not make the commit automatically.
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 First seen · 9 lines · 0 tokens per session scan A 3e416f8063e3
commit-msg is a command published in the GitHub repository jaansokk/cursor_tools (1 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 143 tokens. 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
Git commit with conventional commits format.
deadcode
Find dead code with a configured Knip baseline, then delete it by category behind a ratchet.
update-deps
Audit outdated dependencies, research breaking changes, update one at a time, verify each, commit separately.
commit
Create one conventional commit from an already-scoped change; never push.
release-prep
Review the local working tree, commit, push, open a PR, drive it merge-ready — do not merge.
clean
Repository hygiene — clean temp files, organize execution folders.