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-aesthetics-baseline)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-aesthetics-baseline"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-aesthetics-baseline/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-aesthetics-baseline"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-aesthetics-baseline.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.00447 | $0.00447 |
| Opus 5.5 | $0.00179 | $0.00179 |
| Sonnet 5.5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
pn-aesthetics-baseline 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.
What it actually says
Aesthetics baseline (always)
Applies to user-facing visuals: marketing pages, app UI, auth screens, empty/loading/error states, embedded HTML, static HTML demos, and diagrams (Mermaid in docs or editorial HTML/SVG).
- Project truth: Before styling, read
.pncore-design.mdin the project root when it exists. House philosophy and Primary reference URL there override generic habits. - Cross-project floor: When pn-core MCP is available, load
pn-core://reference/aesthetics-baseline.md(orget_rule("pn-aesthetics-baseline")for this file) and follow it together withget_skill("pn-frontend-design")for implementation detail. - No MCP: Avoid template slop (generic fonts, purple-gradient clichés, identical card grids, center-everything). Use CSS variables, cohesive palette, distinctive typography, orchestrated load motion where appropriate, and respect
prefers-reduced-motion. - Standalone HTML: When the deliverable is a self-contained HTML file, wrap markup in a fenced
```htmlblock, then runget_skill("pn-html-preview")(or follow that command’s save-and-open steps) so the result is checked in a browser. - Workflows: Full UI build →
pn-designorworkflow_step("design", …). Bounded visual change →pn-visual-tweak. Quality pass →pn-frontend-audit. Explore directions →pn-design-variants. Architecture / flowchart / sequence / state / loop / quadrant / layers / process / data-flow / org-chart diagrams →pn-diagramorget_skill("pn-diagram-design")andpn-core://reference/diagram-baseline.md.
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 · 15 lines · 447 tokens per session scan A 14fd231e04a5
pn-aesthetics-baseline is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed yesterday), licensed MIT. It adds 447 tokens to every session, about $0.0018 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.