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/perniemann/pnCoreWrote 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/perniemann/pncore/pn-plugin-quality-gates)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-plugin-quality-gates"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-plugin-quality-gates.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.00000 | $0.00162 |
| Opus 5 | $0.00000 | $0.00081 |
| Sonnet 5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
pn-plugin-quality-gates 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 6d 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
Plugin quality gates
When creating or editing Cursor plugins:
- Ensure
.cursor-plugin/plugin.jsonexists and includes a validname. - Keep paths relative and within the plugin directory (no absolute paths, no
..traversal). - Match declared component paths to real files and folders.
- Include YAML frontmatter for rules, skills, agents, and commands with required metadata.
- Keep plugin scope focused and document installation and usage in
README.md. - Run
npm run validatefrom the repo root to confirm all validators pass before committing.
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.
- 6d ago First seen · 17 lines · 0 tokens per session scan A 75ab7b1c308e
pn-plugin-quality-gates is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 162 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
astro-typescript-cursorrules-prompt-file
Cursor rules for Astro development with TypeScript integration.
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.
nextjs-tailwind-typescript-apps-cursorrules-prompt
Cursor rules for Next.js development with Tailwind CSS and TypeScript integration.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
rules.general
A project rule set for a Next.js application using TypeScript, React, Tailwind CSS, shadcn/ui, Radix UI, and Lucide icons.
react-router
Cursor rule "react-router" from iloveitaly/llm-ide-rules, covering react router, loading mock data, how to use clientloader and loading backend data.