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-delight)<a href="https://agentmods.dev/commands/perniemann/pncore/pn-delight"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-delight/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-delight"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-delight.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.00030 | $0.00779 |
| Opus 5 | $0.00015 | $0.00390 |
| Sonnet 5 | $0.00006 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
pn-delight 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pn-delight
Start every response with: [pn-command] 🔺
Advanced (palette-hidden). Not in the
/slash palette. Invoked by/pn-visual-tweakor/pn-polish, or directly viaget_command("pn-delight").
Add purposeful delight — moments that make the interface feel human and memorable. Every addition must serve a purpose: reduce anxiety, provide feedback, build personality, or reward attention.
When to Use
- Design is functional and complete but feels mechanical
- No micro-interactions or motion
- No moments that make the user smile
- Preparing for a "wow moment" in a demo or launch
The Rule
Every delight element must answer: "What does this communicate or improve?"
- Celebration animation on task completion → reduces anxiety, rewards effort
- Hover animation that reveals secondary action → teaches the interface
- Staggered card entrance on page load → creates a sense of arrival
- Empty state with a custom illustration → humanizes the product
If the answer is "it looks cool" — remove it. That's decoration, not delight.
Flow
1. Context
Check .pncore-design.md for brand personality. Delight must match the brand tone: a data analytics tool gets subtle, precise micro-interactions; a consumer app gets playful, expressive ones.
Load get_skill("pn-animation") and consult the motion taxonomy.
2. Audit What Exists
- Are there any current animations or transitions?
- What states exist that could benefit from motion? (empty → content load, success, error, hover, focus)
- What are the most emotionally resonant moments in this product? (First use? Task completion? Milestone?)
3. Propose Delight Points
Identify 3–5 high-impact moments. For each:
- Where: specific component or interaction
- What: the animation or design detail
- Role: Reveal / Orient / Confirm / Delight (per pn-animation taxonomy)
prefers-reduced-motionfallback
Examples by impact level:
High impact (start here):
- Page load: staggered reveal of key content elements
- Task completion: celebration state (confetti, checkmark animation, color flash)
- First data load: skeleton → content transition with care
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 · 94 lines · 30 tokens per session scan A 9bbf62fcf292
pn-delight is a command published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 779 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-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-cloud-hub
A command for setting up a Cloud Hub and its client automation package, including instructions, a data format, and a test report.
t800-doctor
A command that runs a scripts-only health report for a T-800 or target plugin setup. It reports the version, profile, memory location, state, item counts, always-applied items, and recent audits.
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.