agentmods.dev

pn-render-verify

pn-render-verify is a skill for Cursor from perniemann/pnCore. It costs 48 tokens per session (2,262 once invoked), scanned A, original, MIT.

A review process that examines a rendered visual result, such as an image, screenshot, or HTML page, against its original specification. It reports which required details are visibly present or missing.

In plain words
What is it for?
Use it to verify layouts, visual elements, colours, typography, and other visible requirements in a design or web artifact.
Why use it?
It catches visual differences that configuration or source files alone may hide before the result moves to another review stage.

Skill for Cursor

Written for Cursor: shipped in a Cursor plugin.

Part of the pn-core plugin — 133 skills, 19 commands, 9 agents, 1 MCP server shipped together

not rated 0repo 6d ago A scan 48 tokens original MIT

Good fit Use it to verify layouts, visual elements, colours, typography, and other visible requirements in a design or web artifact.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/perniemann/pncore/pn-render-verify
View source ↗ perniemann/pnCore
Install

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.

Any agent
npx skills add perniemann/pnCore --skill pn-render-verify
Clone the repo
git clone --depth 1 https://github.com/perniemann/pnCore

Made for: Cursor.

Or install pn-core, the plugin that ships this one along with the rest of its 133 skills, 19 commands, 9 agents, 1 MCP server.

Wrote 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.

agentmods badge for pn-render-verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/perniemann/pncore/pn-render-verify/github.svg)](https://agentmods.dev/skills/perniemann/pncore/pn-render-verify)
Your own site
<a href="https://agentmods.dev/skills/perniemann/pncore/pn-render-verify"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-render-verify/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.

agentmods 80×15 button for pn-render-verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/perniemann/pncore/pn-render-verify"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-render-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.02262
Opus 5 $0.00024 $0.01131
Sonnet 5 $0.00010 $0.00452
Haiku 4.5 $0.00005 $0.00226

Measured 9d ago against content hash 0f210de48c8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pn-render-verify 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 9d 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.

packages/pn-core-mcp/content/skills/orchestration/pn-render-verify/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

pn-render-verify

Mission

Read a visual artifact from disk, enumerate spec items against what is visible in the artifact, and emit a structured verifier.contract.json-shaped verdict. The output feeds directly into pn-skeptic-challenge as evidence. Do not assume quality from configuration — only assert what can be observed.

When to use

  • Before invoking pn-skeptic-challenge in "Skeptic on output (post-build)" mode when the deliverable is a render, image, screenshot, or HTML page.
  • Standalone, when a human or orchestrator needs a structured pass/fail verdict on a visual artifact against a spec.

Instructions

  1. Locate the artifact. Identify the output file(s) — renders, screenshots, or HTML pages. Record each path and read the file. Log read_bytes for each artifact.

  2. Load the spec. Retrieve the original discovery spec or design brief (e.g. from discoverySpec, .pncore-design.md, or the plan). Extract acceptance criteria: required visual elements, layout intent, color/typography constraints, and any runtime-specific requirements.

  3. Enumerate spec items. For each spec item, make a direct observation:

    • Assign status: "pass" | "fail" | "partial" | "unknown".
    • Record evidence: a one-sentence description of what is visible (not what was configured).
    • If "fail" or "partial", note what is missing or wrong.

  4. Emit structured verdict in verifier.contract.json shape:

    {
  "acceptance_results": [
    {
      "id": "AC-001",
      "status": "pass | fail | partial | unknown",
      "evidence": "One-sentence observation from the artifact."
    }
  ],
  "test_results": { "status": "unknown | pass | fail", "notes": "" },
  "ci_impact": { "risk": "low | medium | high", "notes": "" },
  "final_recommendation": "ship | ship_with_notes | iterate | block"
}

    Additionally, populate visual_evidence (per skeptic.contract.json extension) for the artifact:

Read the full file on GitHub · 104 lines

Changes

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.

  1. 9d ago First seen · 104 lines · 48 tokens per session scan A 0f210de48c8c

Subscribe to this mod's changes

pn-render-verify is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 2,262 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-09-03.

Design and UXLLMTypeScriptagentscursormcpplugin
Related

Other skills, from other repositories

typescript

TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.

genkit-ai/genkit · 20 tokens

taiyi-diagram-arch

A workflow for turning written system or product architecture into readable, version-controlled diagrams using Mermaid or exported SVG and PNG files. Architecture diagrams show components, boundaries, data flows, and deployment relationships.

Dong90/oh-my-taiyiforge · 48 tokens

taiyi-restyle

A planning guide for breaking a large user-interface redesign into smaller, independently reviewable tasks. A user interface is the part of an application that people see and use.

Dong90/oh-my-taiyiforge · 39 tokens

taiyi-diagram-pipeline

A pipeline that creates and updates architecture diagrams in three stages: a C4 model from the code, an engineering architecture diagram, and an exported PNG image. C4 is a way to describe software architecture at several levels of detail.

Dong90/oh-my-taiyiforge · 52 tokens

taiyi-diagram-render

A tool for rendering existing C4 or architecture Mermaid diagrams as SVG or PNG images. C4 is a way to show software systems at different levels, while Mermaid is a text format for diagrams.

Dong90/oh-my-taiyiforge · 50 tokens

apply-mantel-styles

Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.

sammcj/agentic-coding · 37 tokens