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/SwonVIP/mcp-server-talkWrote 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/rules/swonvip/mcp-server-talk/git-commit-push-workflow)<a href="https://agentmods.dev/rules/swonvip/mcp-server-talk/git-commit-push-workflow"><img src="https://agentmods.dev/badge/rules/swonvip/mcp-server-talk/git-commit-push-workflow/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/rules/swonvip/mcp-server-talk/git-commit-push-workflow"><img src="https://agentmods.dev/badge/rules/swonvip/mcp-server-talk/git-commit-push-workflow.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.00401 | $0.00401 |
| Opus 5.5 | $0.00160 | $0.00160 |
| Sonnet 5.5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
git-commit-push-workflow 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 2mo 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
Git Commit and Push Workflow
General Guidelines
- Commit early and often, with focused changes
- Use descriptive commit messages
- Push changes at logical intervals
When to Commit
- After completing a logical unit of work
- Before switching to another task
- When making significant progress on a feature
- After fixing a bug
- After refactoring code
- After updating documentation
Commit Message Guidelines
- Use the imperative mood (e.g., "Add feature" not "Added feature")
- Start with a capital letter
- Keep the first line under 50 characters
- Add a blank line followed by more details if needed
- Include references to issues/tickets when applicable
Examples of Good Commit Messages
Add MCP server architecture diagram to slide 5
Update security considerations with latest best practices
Fix broken transitions between slides 7 and 8
Refactor slide structure to reduce text content
Push Guidelines
- Push changes at the end of your work session
- Push after completing a feature
- Push before creating a pull request
- Push before moving to a different branch
- Push after resolving merge conflicts
Post-Push Actions
- Verify changes are reflected in the remote repository
- Update collaborators if necessary
- Create or update pull requests if applicable
Emergency Recovery
If you need to recover from a bad commit:
# Undo the last commit but keep changes staged
git reset --soft HEAD~1
# Undo the last commit and discard changes
git reset --hard HEAD~1
# Fix a commit message
git commit --amend -m "New message"
metadata: priority: high version: 1.0 author: AI Assistant
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.
- 2mo ago First seen · 73 lines · 401 tokens per session scan A 29eaeffda46d
git-commit-push-workflow is a cursor rule published in the GitHub repository SwonVIP/mcp-server-talk (0 stars, last pushed 1y ago), licensed MIT. It adds 401 tokens to every session, about $0.0016 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 cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
no-ai-contributors
Never add AI tools as git authors or project contributors.
commits
Conventional Commits standards for clear, semantic commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.