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/vibestackdev/vibe-stackWrote 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/vibestackdev/vibe-stack/git-conventions)<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/git-conventions"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/git-conventions/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/vibestackdev/vibe-stack/git-conventions"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/git-conventions.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.00000 | $0.00177 |
| Opus 5.5 | $0.00000 | $0.00071 |
| Sonnet 5.5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
git-conventions 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 1mo 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 Conventions for Vibe Coders
Commit convention (Conventional Commits):
feat:add user authenticationfix:resolve RLS policy for shared projectschore:update dependenciesdocs:add API documentationrefactor:extract auth helper to separate module
Branch naming:
feature/auth-flowfix/rls-policy-bugchore/update-dependencies
ALWAYS run before commit (if available):
npm run lintnpm run type-checknpm test
AI session workflow:
- Create a new branch before starting any AI session
- Review ALL AI-generated code before committing
- Break large AI generations into multiple focused commits
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.
- 1mo ago First seen · 29 lines · 0 tokens per session scan A f9decd5c5a5c
git-conventions is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 177 tokens. 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
cursor-rules
Rules for placing and organizing Cursor rule files in the repository.
development-workflow
CopilotKit uses a monorepo structure with.
cursorrules
Cursor rule "cursorrules" from CopilotKit/CopilotKit, covering instructions, additional command options and notes.
project-core
Repository-wide project instructions. Canonical rules are in AGENTS.md.
components
React component, styling, theme, accessibility, and RTL instructions.
git-flow
Branching, commits and PR hygiene. Always applies.