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-astro)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-astro"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-astro/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/perniemann/pncore/pn-astro"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-astro.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.00282 | $0.00282 |
| Opus 5.5 | $0.00113 | $0.00113 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
pn-astro 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 2mo 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
Astro rules
- Prefer islands for interactivity; keep as much as possible static/SSG.
- Use
client:*directives only where necessary. Prefer the lightest directive that matches the UX (e.g.client:visiblefor below-fold). - One component per file; PascalCase for components. Use semantic HTML with explicit a11y: one
<h1>per page, descriptivealttext, keyboard focus on interactive elements. - In React islands: follow pn-react conventions for the React portion.
- Content Collections (Astro 2+): Use
defineCollectionwith Zod schemas for typed content; prefergetCollection()over manual file reads. - View Transitions (Astro 3+): Use
<ViewTransitions />for page transitions; respectprefers-reduced-motionand providetransition:animate="none"fallback. - Server Actions / On-demand rendering: Use
output: 'hybrid'oroutput: 'server'withexport const prerender = falsefor dynamic routes; avoid client-side fetching when server rendering is available.
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.
- 2mo ago First seen · 16 lines · 282 tokens per session scan A 4a281823c27d
pn-astro is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed 6d ago), licensed MIT. It adds 282 tokens to every session, about $0.0011 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-31.
Other cursor rules, from other repositories
t-800-mandatory-routing
A mandatory routing rule for creating or changing subagents, skills, commands, rules, and hooks. Hooks are scripts that run automatically when certain events occur.
t-800-operator-routing
A routing rule for explaining Cursor and its agent features to Russian-speaking beginners. Cursor is a code editor with built-in AI assistance.
t-800-factory-routing
A routing rule for building and coordinating groups of coding subagents. Subagents are separate agents that handle parts of a larger task.
t-800-cloud-hub-routing
A routing rule for Cloud Hub setup work, sending matching requests to a designated lead agent. Cloud Hub is the project area named in the rule.
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.