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 jaansokk/cursor_tools --skill commitgit 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/skills/jaansokk/cursor_tools/commit)<a href="https://agentmods.dev/skills/jaansokk/cursor_tools/commit"><img src="https://agentmods.dev/badge/skills/jaansokk/cursor_tools/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/skills/jaansokk/cursor_tools/commit"><img src="https://agentmods.dev/badge/skills/jaansokk/cursor_tools/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.00010 | $0.00196 |
| Opus 5.5 | $0.00004 | $0.00078 |
| Sonnet 5.5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 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 conventional commit message about the changes since the last commit in the current branch.
- Run
git diff --cachedto see staged changes (orgit diffif nothing staged) - Run
git log --oneline -5to see recent commit style
Format:
type(scope): summary— imperative mood, <= 72 chars- Types: feat, fix, refactor, docs, test, chore, style, perf
- 1-2 sentences on the why / impact (not a file-by-file recap)
- Bullet list of changes, grouped by area if scope is wide
- If tests were run, note results. If no coverage or N/A, omit
Present the message as a markdown snippet in chat. Do not make the commit automatically.
$ARGUMENTS
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 · 22 lines · 10 tokens per session scan A f2f6a70e304c
commit is a skill published in the GitHub repository jaansokk/cursor_tools (1 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 196 once invoked, about $0.0000 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 skills, from other repositories
housekeep-dead-code
Remove dead code by category — one commit each, typecheck and tests between, bisect on red — then add a Knip ratchet. Use when "delete the dead code", "remove unused files", or "wire up Knip". Audit first → plan-dead-code. README/deps → workflow-housekeep.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
block-no-verify-hook
Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.
commit-changes-main
Commit directly on main/master when explicitly allowed.
commit-same-branch
Commit on the current branch with conventional message.