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/usrrname/cursorrules/git-commit-push-agentnpx skills add usrrname/cursorrules --skill git-commit-push-agentgit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.00112 | $0.00477 |
| Opus 5 | $0.00056 | $0.00238 |
| Sonnet 5 | $0.00022 | $0.00095 |
| Haiku 4.5 | $0.00011 | $0.00048 |
Grade A, and why
git-commit-push 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 yesterday.
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
Git Commit Standards
Critical Rules
- Use
git statusto check modified or staged files before committing - Never overwrite or push untracked files
- Commits MUST follow the conventional-commit standard
- Always run
git add <filename>from repo root - Use present tense in commit subject ("add" not "added")
- Subject ≤ 72 chars, imperative mood, blank line before body
- Reference issue/ticket with # if used
- Describe what or why, not how changes were made; fixes must state what was fixed
- Keep descriptions brief and focused—avoid verbose explanations
- Include agent name in commit footer ("Commit written by <agent_name>")
Commit Format
<type>(<scope>): <description> (#<issue-number>)
[optional body]
[optional footer]
Commit written by <agent_name>
- If agent not specified, use "cursor agent"
- Types: feat, fix, docs, style, refactor, perf, test, chore, ci, security, rename
Post-Commit Actions
- Do NOT include post-commit commands (e.g.,
npm run lint,git push) in commit message - Suggest these actions separately after commit
Agent Enforcement
- Always check
git statusbefore commit - Never use generic messages ("update code", "commit changes")
- Identify change type per conventional commit
- Commit body should be concise and brief, and should not exceed 20 words
- Prefer single-line descriptions when possible; only use body for essential context
- Use meaningful scope (codebase area)
- Clear, concise, imperative subject
- Add agent name as (co-)author
- Convert user commit instructions to proper format
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.
- yesterday First seen · 51 lines · 0 tokens per session scan A a45fbe13fa9c
git-commit-push is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 112 tokens to every session and 477 once invoked, about $0.0006 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
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.
Remove Old Logs
Remove log files older than 1 day from logs directory.