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.
npx agentmods add skills/espennilsen/pi/penpot-workflownpx skills add espennilsen/pi --skill penpot-workflowgit clone --depth 1 https://github.com/espennilsen/piWrote 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/skills/espennilsen/pi/penpot-workflow)<a href="https://agentmods.dev/skills/espennilsen/pi/penpot-workflow"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/penpot-workflow.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 | $0.00075 | $0.02910 |
| Opus 5 | $0.00037 | $0.01455 |
| Sonnet 5 | $0.00015 | $0.00582 |
| Haiku 4.5 | $0.00007 | $0.00291 |
Grade A, and why
penpot-workflow 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 5d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Penpot Workflow
Step-by-step workflows for managing design work in Penpot via the pi-penpot extension.
Project Setup
When starting a new design project:
- Create the Penpot project with a clear, matching name (same as the code repo)
- Set up standard pages:
Design System— shared components, tokens, and stylesWireframes— low-fidelity layouts and flows- One page per major screen or user flow (e.g.,
Dashboard,Settings,Onboarding)
- Define foundations first:
- Color palette (primary, secondary, neutral, semantic: success/warning/error/info)
- Typography scale (headings h1-h6, body, caption, label, mono)
- Spacing scale (aligned with Tailwind: 4px base unit)
- Border radius tokens
- Shadow/elevation tokens
Shape Creation
Creating shapes with full styling
Use penpot_page tool actions. All shapes support fills, opacity, and rotation on creation.
Rectangles and frames also support r1-r4 for border radius on creation:
penpot_page add-rectangle fileId=X pageId=Y x=0 y=0 width=200 height=100
fills=[{fillColor: "#1E293B", fillOpacity: 1}]
r1=12 r2=12 r3=12 r4=12
Text supports fontSize, fontWeight, fontFamily, fontColor on creation:
penpot_page add-text fileId=X pageId=Y x=0 y=0 width=200 height=40
text="Hello World"
fontSize="24" fontWeight="700" fontFamily="sourcesanspro" fontColor="#FFFFFF"
Available font families
sourcesanspro— Source Sans Pro (default, always available)- Custom fonts can be uploaded via
create-font-variant
Font size and weight are STRINGS
Always pass fontSize and fontWeight as strings: "24" not 24, "700" not 700.
Shape Styling (modify-shape)
After creation, use modify-shape to add advanced styling. First-class params:
Border Radius
penpot_page modify-shape fileId=X pageId=Y shapeId=Z r1=16 r2=16 r3=16 r4=16
r1= top-left,r2= top-right,r3= bottom-right,r4= bottom-left
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.
- 5d ago First seen · 313 lines · 75 tokens per session scan A 65b60f5d569d
penpot-workflow is a skill published in the GitHub repository espennilsen/pi (117 stars, last pushed 13d ago), licensed MIT. It adds 75 tokens to every session and 2,910 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…