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.
npx agentmods add rules/perniemann/pncore/pn-blendergit 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-blender)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-blender"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-blender.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.00318 | $0.00318 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
pn-blender 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 4d 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
Blender rules
- Use Python style consistent with Blender (PEP 8); follow bpy API conventions.
- Never use absolute paths; use relative paths or config/env for project roots.
- Use consistent naming for objects, collections, materials, and meshes (e.g. prefixes: SM_, SK_, M_).
- Blender 4.2+ extension system: For Blender 4.2 and later, create extensions (not add-ons) using the new
bl_info-free manifest format (blender_manifest.toml). For older Blender (<4.2), use add-on registration (register()/unregister()in correct order; unregister in reverse). Annotate which version you are targeting. - Geometry Nodes: Use
bpy.data.node_groups.new(name, 'GeometryNodeTree')andobj.modifiers.new(type='NODES')for procedural meshes. Apply or add a Realize Instances node before export. Prefer Geometry Nodes over particle systems for static distribution in Blender 4.x. - Document export options and target engine when writing export scripts.
- Test scripts in Blender after generating; do not assume they run without verification.
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.
- 4d ago First seen · 16 lines · 318 tokens per session scan A 92e3de2f80db
pn-blender is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 318 tokens to every session, about $0.0016 per session on Opus 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.
Other cursor rules, from other repositories
typescript-conventions
Cursor rule "typescript-conventions" from VirtusLab-Open-Source/strapi-plugin-mcp, covering typescript and coding conventions, typescript configuration, import/export patterns, code organization and services (server/src/services/).
1001-typescript
APPLY TypeScript best practices WHEN writing code TO ensure type safety, readability, and maintainability.
chrome-extension-dev-js-typescript-cursorrules-pro
Cursor rules for VSCode extension development with Electron and TypeScript integration.
javascript-typescript-code-quality-cursorrules-pro
Cursor rules for JavaScript and TypeScript development with code quality integration.
astro-typescript-cursorrules-prompt-file
Cursor rules for Astro development with TypeScript integration.
qwik-tailwind-cursorrules-prompt-file
Cursor rules for Qwik development with Tailwind CSS integration.