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/quinnjr/fruityloops-mcp/git-workflowgit clone --depth 1 https://github.com/quinnjr/fruityloops-mcpWhat 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.00794 | $0.00794 |
| Opus 5 | $0.00397 | $0.00397 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
git-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 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Rules
Critical: Never Bypass Git Hooks
NEVER use --no-verify flag in any git commands.
Git hooks are in place to ensure code quality and workflow compliance. Bypassing them defeats their purpose and can lead to:
- Broken builds on CI/CD
- Code quality issues
- Non-compliant commit messages
- Protected branch violations
❌ FORBIDDEN Commands
# NEVER DO THIS:
git commit --no-verify
git push --no-verify
git commit -n
git push -n
✅ Correct Approach
If a git hook fails:
- Read the error message - it tells you what's wrong
- Fix the issue - address the linting, formatting, or validation error
- Commit normally - let the hooks validate your changes
# If pre-commit fails:
uv run ruff check --fix .
uv run ruff format .
git add .
git commit -m "fix: your message"
# If tests fail:
uv run pytest
# Fix failing tests, then commit
# If commit message format is wrong:
# Use conventional commits format
git commit -m "feat: add new feature"
Git-Flow Branching
Branch Types
main- Production code (protected)develop- Development integration (protected)feature/*- New featuresbugfix/*- Bug fixeshotfix/*- Production fixesrelease/*- Release preparationgh-pages- Documentation (auto-managed)
Branch Creation
# Feature
git checkout develop
git checkout -b feature/descriptive-name
# Bugfix
git checkout develop
git checkout -b bugfix/issue-description
# Hotfix
git checkout main
git checkout -b hotfix/critical-fix
# Release
git checkout develop
git checkout -b release/v1.1.0
Protected Branches
Never push directly to:
maindevelop
Always use Pull Requests for these branches.
Commit Message Format
Follow Conventional Commits specification:
type(scope): description
[optional body]
[optional footer]
Valid Types
feat: New featurefix: Bug fixdocs: Documentationstyle: Formatting (no code change)refactor: Code restructuringtest: Adding/updating testschore: Maintenance tasksperf: Performance improvementci: CI/CD changesbuild: Build system changes
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 · 144 lines · 794 tokens per session scan A 38ad15df6da4
git-workflow is a cursor rule published in the GitHub repository quinnjr/fruityloops-mcp (5 stars, last pushed 8mo ago), licensed MIT. It adds 794 tokens to every session, about $0.0040 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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.