Prisma ORM is a Node.js and TypeScript database toolkit that lets applications work with databases through a programming interface instead of writing every query directly in SQL. Developers use it with databases including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB, and CockroachDB. The catalogue add-ons provide agent rules, skills, hooks, agents, and other workflows for using Prisma.
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/prisma/ormWrote 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/prisma/orm/git-staging)<a href="https://agentmods.dev/rules/prisma/orm/git-staging"><img src="https://agentmods.dev/badge/rules/prisma/orm/git-staging/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/prisma/orm/git-staging"><img src="https://agentmods.dev/badge/rules/prisma/orm/git-staging.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.00744 | $0.00744 |
| Opus 5.5 | $0.00298 | $0.00298 |
| Sonnet 5.5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
git-staging 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- git-staging — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Best Practices
Never Use git add -A or git add .
CRITICAL: Do not use git add -A, git add ., or git add --all when staging changes. These commands stage all changes including unrelated or untracked files.
Correct Approach
Always stage files explicitly:
# Stage specific files
git add path/to/file1.ts path/to/file2.ts
# Stage modified files only (doesn't add untracked files)
git add -u
# Stage files matching a pattern (be specific)
git add packages/1-framework/1-core/*/package.json
Always Sign Off Commits
CRITICAL: Every git commit you author MUST include a Signed-off-by: trailer. Pass -s (or --signoff) on every commit.
# Correct
git commit -s -m 'fix(foo): correct null handling in bar'
# Correct (with HEREDOC for multi-line messages)
git commit -s -m "$(cat <<'EOF'
fix(foo): correct null handling in bar
Explains why ...
EOF
)"
# WRONG — no signoff trailer
git commit -m 'fix(foo): correct null handling in bar'
Common pitfalls:
- The
format.signoff=truegit config option only affectsgit format-patch, notgit commit. Do not assume the user's global config will add the trailer. - There is no
commit.signoffgit config option. The trailer must be added explicitly per commit, or via aprepare-commit-msghook owned by the user. - When using
git commit --amend(rare — see "Never Amend Pushed Commits" below), pass--signoffto ensure the trailer is present after the amend. - When rebasing with
--execor--signoff, ensure the trailer is preserved.
Verify before pushing:
# Last commit must show a Signed-off-by line under the message body
git log -1 --format='%B' | tail -3
Never Amend Pushed Commits
Do not use git commit --amend on commits that have already been pushed to the remote. This rewrites history and causes problems for anyone else working with the branch.
Instead, create a new commit with the fix.
Best Practices
- Review before staging: Run
git statusto see what will be staged - Stage explicitly: List the specific files or use
-ufor modified files only - Verify before committing: Run
git diff --cachedto review staged changes - Sign off every commit: Pass
-sto everygit commitinvocation - Keep commits focused: Each commit should contain related changes only
- Don't amend pushed commits: Only amend commits that haven't been pushed yet
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 · 86 lines · 744 tokens per session scan A 5d206d2271e0
git-staging is a cursor rule published in the GitHub repository prisma/orm (47,693 stars, last pushed today), licensed Apache-2.0. It adds 744 tokens to every session, about $0.0030 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-30.
Other cursor rules, from other repositories
prisma
Prisma database patterns and conventions for Next.js and TypeScript projects.
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
security-archive
Socket.dev security data integration and security selectors.
code-validation-workflow
Code validation workflow (format, lint, test, coverage, typecheck).
git
Git workflow and commit rules.