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 rules/swonvip/mcp-server-talk/git-commit-push-workflowgit clone --depth 1 https://github.com/SwonVIP/mcp-server-talkWhat 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.00401 | $0.00401 |
| Opus 5 | $0.00200 | $0.00200 |
| Sonnet 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 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 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.
- yesterday 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.0020 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.