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/shawnfromportland/agentmemoryforcursor/git_workflow_rulesgit clone --depth 1 https://github.com/shawnfromportland/agentmemoryforcursorWhat 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.00019 | $0.01472 |
| Opus 5 | $0.00010 | $0.00736 |
| Sonnet 5 | $0.00004 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
git_workflow_rules 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Name: Git Workflow Automation
Description:
This rule outlines how the AI assistant should handle requests to commit or discard changes using the custom npm scripts. The goal is to streamline the development workflow by automating these common Git operations based on natural language commands from the user.
Committing Changes
-
Trigger:
- For commit ONLY (local): User asks to "commit," "commit changes," "commit this," "commit the latest," or similar explicit phrasing indicating a desire to save work locally.
- For commit AND PUSH: User asks to "commit and push," "save and sync," or similar explicit phrasing indicating a desire to save work and update the remote repository.
- For PUSH ONLY: User asks to "push," "push changes," "sync remote," or similar explicit phrasing indicating a desire to update the remote repository with already committed changes.
-
Clarify Ambiguity (If Necessary):
- If the user's request to commit (from Trigger) is vague or could be interpreted in multiple ways (e.g., "should we save this?"), the AI MUST first seek clarification: "It sounds like you might want to commit the changes. Is that correct?"
- If clarification was sought and the user confirms they do not want to commit, the process stops here. The subsequent steps are only followed if the intent to commit is clear (either initially explicit or clarified as such).
-
Generate Commit Message and Detailed Changelog Content:
- The AI will silently review changes made during the current interactive session leading up to the commit request.
- The AI will generate a concise, conventional commit message (e.g., "feat: Implement user authentication flow").
- The AI will also generate a list of key changes/features/fixes from the session as bullet points.
- The AI will format this as a markdown block: the commit message as
### Title, followed by the bullet points. Example:### feat: New user dashboard and API refactor - Created `UserDashboard.tsx` with initial metrics display. - Modified `/api/users` endpoint to support pagination. - Refactored `AuthService` to use JWT tokens.
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 · 77 lines · 19 tokens per session scan A d50d3f3c8296
git_workflow_rules is a cursor rule published in the GitHub repository shawnfromportland/agentmemoryforcursor (11 stars, last pushed 1y ago), licensed MIT. It adds 19 tokens to every session and 1,472 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-30.
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.