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/commands/perniemann/pncore/pn-audit-typography)<a href="https://agentmods.dev/commands/perniemann/pncore/pn-audit-typography"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-audit-typography/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/commands/perniemann/pncore/pn-audit-typography"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-audit-typography.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.00038 | $0.00593 |
| Opus 5 | $0.00019 | $0.00296 |
| Sonnet 5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
pn-audit-typography 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pn-audit-typography
Start every response with: [pn-command] 🔺
Advanced (palette-hidden). Not in the
/slash palette. Invoked by the/pn-frontend-auditumbrella, or directly viaget_command("pn-audit-typography").
Focused typography pass: audit type scale, font choices, loading behavior, hierarchy, and readability. No layout changes (use pn-audit-layout), no color changes (use pn-colorize) — typography only.
Flow
1. Context
Check .pncore-stack.md and target files/pages. If scope is unclear, ask: "Which pages or components should I audit? (landing / all / specific paths)"
2. Audit
Load get_skill("pn-frontend-design-philosophy") for the typography scoring rubric (Phase 2).
Type scale:
- Is there a distinct display / reading / utility layer?
- Are font sizes from a defined scale (e.g. 4px grid, modular scale)?
- Body text ≥ 16px for reading contexts?
- Line height 1.4–1.7 for body, tighter for display?
Font choices:
- Distinctive, characterful typeface (not default Inter / Geist / system-ui)?
- Strong contrast between display font and body font?
- Web fonts loaded via
font-display: swap? - Fallback stack defined?
Hierarchy:
- Clear visual weight difference between heading levels?
- No more than 2–3 font families on a single page?
- Consistent heading sizing across routes?
Accessibility:
- All body text ≥ 4.5:1 contrast ratio?
- No text over busy backgrounds without overlay?
- Small caps / all-caps only on short strings (≤20 chars)?
Output: numbered issues table (location | issue | severity | suggested fix). Save to docs/audits/.
Gate: Present issues for triage. Apply fixes only after confirmation.
3. Fix
Apply in severity order:
- Wrong font → update CSS variable and fallback stack
- Missing
font-display: swap→ add to@font-faceor Google Fonts URL - Broken scale → introduce CSS custom properties for type steps
- Contrast failure → darken text or lighten background per brand tokens
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.
- 8d ago First seen · 66 lines · 38 tokens per session scan A cf7c017a91ac
pn-audit-typography is a command published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 593 once invoked, about $0.0002 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 commands, from other repositories
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…
ux-copy
Microcopy review and rewrite against the voice rubric. Produces a before/after table with severity per string and a clean rewrite block. Triggers on "review the copy", "fix the microcopy", "the error messages are bad", or "rewrite this". Use when reviewing or rewriting microcopy, fixing error messages that sound like…
build-website
Build a small site with the simplest stack that fits, fast by default and editable afterwards.