Borrowing it
Nothing to install: this file belongs to perniemann/pnCore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/perniemann/pnCore/main/CLAUDE.mdgit 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/instructions/perniemann/pncore/claude-md)<a href="https://agentmods.dev/instructions/perniemann/pncore/claude-md"><img src="https://agentmods.dev/badge/instructions/perniemann/pncore/claude-md.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.00447 | $0.00447 |
| Opus 5 | $0.00224 | $0.00224 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
pnCore CLAUDE.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude / agent instructions (pnCore workspace)
This repository maintains the pnCore plugin and MCP server. When working on user-facing UI in this repo or in downstream projects that use pnCore, follow the design context in .pncore-design.md when present.
Frontend aesthetics (global)
<frontend_aesthetics> You tend toward generic, on-distribution outputs. In frontend design that reads as "AI slop." Avoid it: ship creative, context-specific interfaces that match the project's .pncore-design.md when present.
Typography: Distinctive, characterful fonts; strong display vs body contrast. Do not default to Inter, Roboto, Arial, Geist, or system-ui stacks unless the project spec explicitly requires them.
Color and theme: One cohesive system via CSS variables; dominant base with sharp accents; tinted neutrals where appropriate. Avoid clichéd purple-blue gradients on white and cyan-on-dark template accents unless on-brand.
Motion: Prefer one well-orchestrated load sequence (staggered reveal with clear hierarchy) over many unrelated micro-motions. Tag each animation with a role: Reveal, Orient, Confirm, or Delight. Respect prefers-reduced-motion.
Backgrounds: Add depth when the aesthetic allows—gradients, grain, geometric patterns, layered surfaces—not flat default fills everywhere.
Anti-slop: No identical card grids with no variation, no glassmorphism-everywhere, no gradient text on every heading, no center-everything layouts without intent.
Project truth: When .pncore-design.md exists, treat it as authoritative for audience, personality, ambition, reference feel, house philosophy, primary reference URL, and constraints. When it conflicts with generic habits, follow the file. </frontend_aesthetics>
pnCore resources
- Full checklist:
pn-core://reference/aesthetics-baseline.md(MCP) orpackages/pn-core-mcp/content/reference/aesthetics-baseline.md - Always-apply rule:
pn-aesthetics-baseline(pluginrules/after install) - After editing canonical content under
packages/pn-core-mcp/content/, runnpm run sync:content
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.
- 5d ago First seen · 28 lines · 447 tokens per session scan A 3f3dfa08f0da
pnCore CLAUDE.md is an instructions file published in the GitHub repository perniemann/pnCore (0 stars, last pushed 3d ago), licensed MIT. It adds 447 tokens to every session, about $0.0022 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.