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-vanilla-web)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-vanilla-web"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-vanilla-web.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.00216 | $0.00216 |
| Opus 5 | $0.00108 | $0.00108 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
pn-vanilla-web 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 3d 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
Vanilla web rules
- Use semantic HTML:
<header>,<main>,<nav>,<footer>,<article>,<section>,<aside>. - Prefer progressive enhancement: content works without JavaScript; JS adds interactivity.
- Use consistent class naming: BEM or kebab-case. Avoid inline styles for layout; use CSS classes.
- CSS variables for theming (colors, spacing, typography); reference pn-design-system for token structure.
- A11y: one
<h1>per page, labels for form controls, logical heading order, focus order. - Responsive and touch: mobile-first; min 44×48px touch targets; no hover-only for critical actions; never disable zoom.
- Keep JS minimal; no unnecessary libraries unless required by the feature.
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.
- 3d ago First seen · 16 lines · 216 tokens per session scan A e743869b654a
pn-vanilla-web is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed today), licensed MIT. It adds 216 tokens to every session, about $0.0011 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-09-03.
Other cursor rules, from other repositories
nextjs-typescript-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript and Tailwind CSS integration.
nextjs-tailwind-typescript-apps-cursorrules-prompt
Cursor rules for Next.js development with Tailwind CSS and TypeScript integration.
qwik-tailwind-cursorrules-prompt-file
Cursor rules for Qwik development with Tailwind CSS integration.
nextjs
Next.js with TypeScript and Tailwind UI best practices.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
design
All tasks related to updating frontend components, CSS, and general styling.