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-layout)<a href="https://agentmods.dev/commands/perniemann/pncore/pn-audit-layout"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-audit-layout.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.00035 | $0.00519 |
| Opus 5 | $0.00017 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
pn-audit-layout 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 7d 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
pn-audit-layout
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-layout").
Focused layout pass: audit spacing tokens, grid usage, component rhythm, and responsive breakpoints. No typography changes (use pn-audit-typography), no color changes (use pn-colorize) — layout only.
Flow
1. Context
Check .pncore-stack.md and target scope. Ask if unclear: "Which pages or layout components should I audit?"
2. Audit
Load get_skill("pn-frontend-design-philosophy") for the layout scoring rubric (Phase 3).
Spacing tokens:
- Is there a consistent spacing scale (e.g. 4px or 8px grid)?
- Are arbitrary pixel values used instead of tokens?
- Do padding/margin values match the scale?
Grid system:
- Is a grid defined (CSS Grid / Flexbox layout container)?
- Are columns consistent across similar content types?
- Do full-bleed sections align to the defined max-width?
Component rhythm:
- Do card / list item sizes match?
- Is vertical rhythm consistent (equal spacing between sections)?
- No "identical card grids with zero variation" anti-pattern?
Responsive behavior:
- Breakpoints defined in tokens / CSS variables?
- Mobile-first or correct media query order?
- Content reflow tested at 360px, 768px, 1440px?
Output: numbered issues table (location | issue | severity | suggested fix). Save to docs/audits/.
Gate: Present issues for triage. Apply fixes after confirmation.
3. Fix
Apply in severity order:
- Arbitrary values → replace with nearest token
- Missing grid container → add layout wrapper with defined columns
- Broken mobile layout → add responsive breakpoints
4. Summary
Table: issues found → issues fixed. Ref pn-arrange for visual arrangement refinement.
Skills to use
- pn-frontend-design-philosophy — Phase 3 scoring rubric (Layout + CSS System Audit)
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.
- 7d ago First seen · 63 lines · 35 tokens per session scan A bc92f8c7eeaa
pn-audit-layout is a command published in the GitHub repository perniemann/pnCore (0 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 519 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
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…
t800-fix
A command for making a narrow, predefined fix to existing agents, skills, commands, rules, or hooks. A fix-pack is a file listing the exact changes to make.
t-800-factory
A command that delegates creation or integration of a subagent to the T-800 Factory. It passes the proposed role, category, permissions, callers, and existing registry information to that factory.
stripe-backend
Centralized LLM prompt instructions for Copilot and Cursor, including scripts to convert and sync rules for Python, React, Shell, and TypeScript. Designed for rapid reuse and contribution across projects.
t-800-health
bash scripts/health-check.sh.
react
Apply React with TypeScript best practices.