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 skills/emaraschio/cursor-commands/commit-changes-mainnpx skills add emaraschio/cursor-commands --skill commit-changes-maingit clone --depth 1 https://github.com/emaraschio/cursor-commandsWhat 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.00013 | $0.00276 |
| Opus 5 | $0.00006 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
commit-changes-main 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
Overview
Commit changes to the main branch of a GitHub repository with proper commit message.
Steps
-
Prepare branch
- Ensure all changes are committed to the correct branch using the conventional commit message convention
- Push changes to remote
- Verify changes are up to date with main
-
Write commit message
- Must use the conventional commit message convention.
- Summarize changes clearly
-
Commit changes
- Use a single commit for the changes
- Commit the changes to the main branch
- Push the main branch to the remote repository
Commit Message Examples
feat: add new feature
fix: fix bug
chore: update dependencies
refactor: refactor code
test: add tests
docs: update documentation
Guardrails
- Commit to main only with explicit consent; otherwise move the work to a separate branch.
- Never force-push main or any shared branch; reconcile with a normal pull or merge instead.
- Use the Conventional Commits convention for every message.
- Never print, stage, or commit secrets or credential files (.env, .env.*, keys); exclude them and warn instead.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 42 lines · 13 tokens per session scan A 852326b78aee
commit-changes-main is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 276 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 skills, from other repositories
commit
Prepare and propose a commit. Use when the user asks to commit, prepare a commit, or similar. Never commits without explicit approval.
phase-summary
Produce the deliverables summary at the end of a task loop. Always run before preparing a commit.
managing-git
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.
git-commit
This skill should be used BEFORE running any git commit command. Triggers when about to run git commit. Ensures commit messages follow Conventional Commits specification and prompts for the Jira ticket number.
git-commit
How to write a commit message that stays meaningful after the session ends — explain WHY, follow the repository's convention, and never reference conversation-local structure like "Phase 2" or "Task 3". Load this BEFORE running git commit, whenever creating a commit, amending a commit message, or asked to "commit…
ship-it
End-to-end ship loop: atomic commits, PR, tiered review (lite|heavy), fix every finding, re-review until zero remain, then merge-commit. lite runs a single /review pass; heavy spins up a dynamic Workflow with diff-aware review personas plus a Codex cross-model peer. Use when Stevie says "/ship-it", "ship it", "ship…