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/no-pull-request-target)<a href="https://agentmods.dev/rules/prisma/orm/no-pull-request-target"><img src="https://agentmods.dev/badge/rules/prisma/orm/no-pull-request-target/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/no-pull-request-target"><img src="https://agentmods.dev/badge/rules/prisma/orm/no-pull-request-target.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.00027 | $0.00496 |
| Opus 5.5 | $0.00011 | $0.00198 |
| Sonnet 5.5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
no-pull-request-target 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:
- no-pull-request-target — 100% identical, 0 lines differ
What it actually says
Forbidden: pull_request_target
Do not introduce the pull_request_target event trigger in any workflow under .github/workflows/. CI enforces this via scripts/lint-workflow-triggers.mjs, which fails the Lint job if the token appears anywhere in a workflow file outside a YAML comment.
Why
pull_request_target runs in the base repository's trust context — it has secrets and a writable GITHUB_TOKEN — but it fires for PRs from forks. If such a workflow ever executes the PR's code, directly or transitively (e.g. via a shared cache restored from a fork-PR run, or a third-party action that interpolates PR metadata into a shell command), fork-controlled code runs with the base repo's permissions. This is GitHub's "Pwn Request" pattern.
It was the entry point of the May 2026 TanStack supply-chain compromise that published 84 malicious npm versions across 42 @tanstack/* packages.
- TanStack postmortem: https://tanstack.com/blog/npm-supply-chain-compromise-postmortem
- GitHub Security Lab on Pwn Requests: https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/
What to use instead
pull_request— runs with a read-onlyGITHUB_TOKENand zero secrets when the PR comes from a fork (GitHub default; we rely on it).- For commenting on PRs from a privileged side, prefer the
workflow_runtrigger paired with strict input validation, or schedule a job that reads PR metadata via the API rather than running the PR's code.
If you genuinely need it
Don't paper over the lint with a per-file override. Open a PR that:
- Justifies the use case to code owners.
- Demonstrates that the workflow does not check out, build, install, or otherwise execute fork-controlled content.
- Updates
scripts/lint-workflow-triggers.mjsto reflect the new policy (e.g. an explicit allow-list keyed on filename and event declaration shape).
See docs/oss/supply-chain.md for the broader fork-PR posture.
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 · 33 lines · 27 tokens per session scan A 85877984cf07
no-pull-request-target is a cursor rule published in the GitHub repository prisma/orm (47,693 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 496 once invoked, about $0.0001 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.
ultracite
Ultracite enforces strict type safety, accessibility standards, and consistent code quality for JavaScript/TypeScript projects using Biome's lightning-fast formatter and linter.
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.
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.