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/rules/perniemann/pncore/pn-visual-indicator)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-visual-indicator"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-visual-indicator/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/rules/perniemann/pncore/pn-visual-indicator"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-visual-indicator.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.00807 | $0.00807 |
| Opus 5.5 | $0.00323 | $0.00323 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
pn-visual-indicator 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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual indicator
When the response was touched by pnCore this turn (see definition below), begin the response with a context tag followed by 🔺:
[pn-default] 🔺— rules / default / no specific command or agent active.[pn-command] 🔺— your system prompt is a pn command (e.g.pn-new,pn-setup).[pn-agent] 🔺— your system prompt is a pn agent (e.g.pn-project-builder,pn-reviewer).[pn-skill] 🔺— responding primarily as a skill.[pn-plan] 🔺— Cursor IDE plan mode is active.
Use exactly one tag and one 🔺 (Unicode U+1F53A — emoji red triangle pointed up). A single space between tag and 🔺 is allowed for readability. The triangle is the same red emoji in every context; the [pn-*] text tag carries the context so clients/userscripts can still parse, filter, or restyle by context.
The emoji glyph is canonical because Cursor's chat does not apply our assets/pn-indicator.css to assistant markdown — the plain Unicode ▲ (U+25B2) inherits chat default text color (white/grey on dark themes). Emoji code points carry their own color and render red on every mainstream platform without CSS.
"Touched by pnCore" definition
Tag the response if any of the following happened this turn:
- Called a tool from the
pn-core-mcpMCP server (e.g.list_skills,get_skill,workflow_step,health,approval_checkpoint,list_workflow_types). - Read or applied a pnCore skill (
packages/pn-core-mcp/content/skills/**/SKILL.mdor its synced plugin copy underplugins/pnCore/skills/). - The active system prompt is a pnCore command (
/pn-*) or agent (pn-*fromagents/oragents-internal/). - A
pn-*rule was actually consulted as authoritative for the content of this response. - A pnCore MCP resource was fetched (e.g.
pn-core://reference/aesthetics-baseline.md).
Do not tag a response solely because this rule (or any other alwaysApply pn rule) is loaded into context. Mere presence of a pn rule file is not a "touch" — there must be an actual contribution from a pn surface to the response.
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.
- 1mo ago First seen · 43 lines · 807 tokens per session scan A b2f062c4861e
pn-visual-indicator is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 807 tokens to every session, about $0.0032 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
t-800-mandatory-routing
A mandatory routing rule for creating or changing subagents, skills, commands, rules, and hooks. Hooks are scripts that run automatically when certain events occur.
t-800-operator-routing
A routing rule for explaining Cursor and its agent features to Russian-speaking beginners. Cursor is a code editor with built-in AI assistance.
t-800-factory-routing
A routing rule for building and coordinating groups of coding subagents. Subagents are separate agents that handle parts of a larger task.
t-800-cloud-hub-routing
A routing rule for Cloud Hub setup work, sending matching requests to a designated lead agent. Cloud Hub is the project area named in the rule.
typescript-conventions
Cursor rule "typescript-conventions" from VirtusLab-Open-Source/strapi-plugin-mcp, covering typescript and coding conventions, typescript configuration, import/export patterns, code organization and services (server/src/services/).
1001-typescript
APPLY TypeScript best practices WHEN writing code TO ensure type safety, readability, and maintainability.