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/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/git-workflows)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/git-workflows"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/git-workflows.svg" alt="Measured on agentmods" 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.00011 | $0.00972 |
| Opus 5 | $0.00005 | $0.00486 |
| Sonnet 5 | $0.00002 | $0.00194 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
git-workflows 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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: git-workflows
Cursor Agent-Requested Rule — applied when AI determines relevance.
Git Workflows - Version Control Best Practices
Clean history, clear intent, collaborative development.
Branching Strategies
Git Flow
main ●────────────────────────●
╲ ╱
develop ●──●──●──●──●──●──●──●
╲ ╲ ╱ ╱
feature/A ●────●────● ╱
feature/B ●────●────●
hotfix ●──●
| Branch | Purpose | Lifetime |
|---|---|---|
main |
Production-ready code | Permanent |
develop |
Integration branch | Permanent |
feature/* |
New features | Temporary |
release/* |
Release preparation | Temporary |
hotfix/* |
Urgent production fixes | Temporary |
Trunk-Based Development
main ●──●──●──●──●──●──●──●──●──●──●
╲ ╲ ╲ ╲ ╲ ╲
PR ●────● ●────● ●────●
- Short-lived feature branches (< 1 day)
- Continuous integration to
main - Feature flags for incomplete features
Commit Conventions
Conventional Commits
<type>(<scope>): <description>
[optional body]
[optional footer]
Types:
feat:— New featurefix:— Bug fixdocs:— Documentation onlystyle:— Formatting, no code changerefactor:— Code restructuringtest:— Adding/updating testschore:— Build, dependencies
Examples:
feat(auth): add OAuth2 login with Google
fix(api): resolve null pointer in user validation
refactor(database): migrate from MongoDB to PostgreSQL
BREAKING CHANGE: removed deprecated v1 endpoints
Commit Best Practices
| ✅ DO | ❌ DON'T |
|---|---|
| Write in imperative mood | "Fixed bug" → "Fix bug" |
| Keep subject under 50 chars | Long, rambling descriptions |
| Reference issues | No context about why |
| Separate subject from body | Everything in one line |
Pull Request Workflow
PR Template
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.
- 4d ago First seen · 188 lines · 11 tokens per session scan A 2c96cea0fad9
git-workflows is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 972 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.