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-arrange)<a href="https://agentmods.dev/commands/perniemann/pncore/pn-arrange"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-arrange/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-arrange"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-arrange.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.00036 | $0.00539 |
| Opus 5 | $0.00018 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
pn-arrange 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pn-arrange
Start every response with: [pn-command] 🔺
Advanced (palette-hidden). Not in the
/slash palette. Invoked by/pn-design(Layout substep),/pn-visual-tweak, or/pn-polish, or directly viaget_command("pn-arrange").
Focused layout pass: fix spacing rhythm, layout composition, grid patterns, and visual hierarchy through space. No font or color changes — spatial design only.
Flow
1. Scope
If not specified: "Which section, component, or page should I focus on? Or 'all' for the full project."
2. Audit
Load get_skill("pn-grid-systems") and consult [reference/spatial-design.md](../skills/frontend/reference/spatial-design.md).
Audit for:
- Rhythm: Is the same spacing used everywhere? Is there contrast between tight (within-component) and generous (between sections) spacing?
- Named anti-patterns: Identical card grid? Center-everything layout? Same padding throughout? Hero metric layout? Cards nested in cards?
- Composition: Symmetric and centered, or asymmetric and dynamic?
- Grid-breaking: Are there any elements that intentionally escape the grid for emphasis?
- Spacing tokens: Are raw px values used instead of tokens?
- Container queries: For components appearing in multiple contexts (sidebar vs main), are container queries used?
- Negative space: Does the layout use deliberate emptiness for emphasis, or is every pixel filled?
Output issues. Gate on confirmation before fixing.
3. Fix
Apply changes. Common fixes:
- Introduce spacing scale with contrast (tight groupings, generous section separators)
- Break symmetric centering with offset compositions (60/40 split, left-aligned hero)
- Replace identical card grid with editorial rhythm (featured + standard)
- Extract spacing values to tokens
- Add container queries for reusable components
- Add generous negative space around key elements
4. Summary
What was changed, spatial anti-patterns resolved, composition shift if applicable.
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 · 55 lines · 36 tokens per session scan A 42dc4778c2a2
pn-arrange is a command published in the GitHub repository perniemann/pnCore (0 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 539 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
t800-start
A single command for creating or updating development helpers such as rules, skills, commands, subagents, and hooks. It can target a plugin, the current project, or shared settings.
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.
t800-loop
A semi-manual workflow for reviewing the results of a previous development run and preparing a queue of fixes. HITL means a human reviews or approves the queued work before fixes are applied in batches.
t800-audit
A command for auditing a Cursor setup, including its rules, skills, commands, agents, and plugins. It identifies which parts are useful and which consume unnecessary context, meaning the instructions an AI reads before working.
t800-onboard
A command for newcomers that explains what is installed in Cursor globally and in the current project, plus what the T-800 team can do.
t800-cloud-hub
A command for setting up a Cloud Hub and its client automation package, including instructions, a data format, and a test report.