git-and-monorepo

git-and-monorepo is a cursor rule for Cursor from BetterTyped/hype-stack. It costs 329 tokens per session, scanned A, original, MIT.

Repository rules for commit messages and for working in a pnpm/Nx monorepo, which is one repository containing multiple related projects or packages.

In plain words
What is it for?
Use them when writing commits or changing code in a project managed with pnpm and Nx.
Why use it?
They keep commits consistent and help changes follow the repository's package-management and workspace structure.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them when writing commits or changing code in a project managed with pnpm and Nx.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/bettertyped/hype-stack/git-and-monorepo
Install

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.

Clone the repo
git clone --depth 1 https://github.com/BetterTyped/hype-stack

Made for: Cursor.

Wrote 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.

agentmods badge for git-and-monorepo

README.md
[![agentmods](https://agentmods.dev/badge/rules/bettertyped/hype-stack/git-and-monorepo/github.svg)](https://agentmods.dev/rules/bettertyped/hype-stack/git-and-monorepo)
Your own site
<a href="https://agentmods.dev/rules/bettertyped/hype-stack/git-and-monorepo"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/git-and-monorepo/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.

agentmods 80×15 button for git-and-monorepo

Your own site · 80×15
<a href="https://agentmods.dev/rules/bettertyped/hype-stack/git-and-monorepo"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/git-and-monorepo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 329 This file is loaded in full into every session.
When invoked 329 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00329 $0.00329
Opus 5.5 $0.00132 $0.00132
Sonnet 5.5 $0.00066 $0.00066
Haiku 4.5 $0.00033 $0.00033

Measured 1mo ago against content hash a6aabce69f30, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-and-monorepo 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.

.cursor/rules/git-and-monorepo.mdc · 30 lines

What it actually says

Git and Monorepo

Commit messages

Commits follow the conventional-commit + git-cz emoji style already in the history:

  • feat: 🎸 <subject> — new feature
  • fix: 🐛 <subject> — bug fix
  • fix: 💄 <subject> — visual/style fix
  • chore: <subject> — tooling, deps, housekeeping
  • refactor: <subject> — behavior-preserving restructuring
  • docs: ✏️ <subject> — documentation

Subject is imperative and lowercase ("add invitation flow", not "Added invitation flow."). Match this format exactly when authoring commits.

Monorepo

pnpm workspaces + Nx.

  • Internal packages are @hype-stack/* and referenced with "workspace:*" — never a version number.
  • Shared code used by multiple apps lives in packages/; code used by one app stays inside that app. Don't promote to packages/ until a second real consumer exists.
  • Run app-scoped scripts with pnpm --filter @hype-stack/<app> <script>; repo-wide targets run through the root scripts (Nx handles caching and ordering).
  • Add dependencies to the specific app or package that uses them, not the workspace root (root is for tooling only).
  • After changing generated types or cross-app contracts (backend routes, socket events, enums), regenerate with pnpm generate so dependent apps pick up the new types.
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.

  1. 1mo ago First seen · 30 lines · 329 tokens per session scan A a6aabce69f30

Subscribe to this mod's changes

git-and-monorepo is a cursor rule published in the GitHub repository BetterTyped/hype-stack (12 stars, last pushed 15d ago), licensed MIT. It adds 329 tokens to every session, about $0.0013 per session on Opus 5.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.