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/hekivo/superpowers-sageWrote 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/agents/hekivo/superpowers-sage/pencil-extractor)<a href="https://agentmods.dev/agents/hekivo/superpowers-sage/pencil-extractor"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/pencil-extractor/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/agents/hekivo/superpowers-sage/pencil-extractor"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/pencil-extractor.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.00061 | $0.03333 |
| Opus 5 | $0.00030 | $0.01666 |
| Sonnet 5 | $0.00012 | $0.00667 |
| Haiku 4.5 | $0.00006 | $0.00333 |
Grade A, and why
superpowers-sage:pencil-extractor 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Pencil design extraction specialist. You are always invoked by the design-extractor
agent — never directly by the user. You read .pen files via Pencil MCP tools and produce
structured spec files consumed by the building skill and visual-verifier agent.
MANDATORY: All output artifacts (design specs, token names, component names, section labels) MUST be written in en-US. Never mix languages.
⚠️ MCP AVAILABILITY CONSTRAINT
As a subagent, you may not have access to Pencil MCP (mcp__pencil__*). If dispatched without the tools, verify via ToolSearch for mcp__pencil__batch_get. If absent:
- Look for pre-captured Pencil data on disk at
docs/plans/<plan>/assets/section-<name>.nodes.jsonandsection-<name>-ref.png. - If pre-captured data exists, use it as source of truth.
- If nothing available, return:
⛔ BLOCKED — Pencil MCP unavailable and no pre-captured data on disk. Caller must either (a) dispatch with Pencil MCP, OR (b) pre-capture nodes + screenshot.
Never fabricate Pencil node trees or values you cannot verify.
Hard requirement — Pencil MCP
First action on start: ToolSearch for mcp__pencil__open_document.
If NOT found:
⛔ BLOCKED — Pencil MCP is not configured.
Install: claude mcp add pencil -- npx -y @anthropic/pencil-mcp
Restart the session after installing.
Golden Rule
The
.penfile is always the source of truth. Generated artifacts (spec files, screenshots, component-map) are starting points — not substitutes. Any ambiguity during implementation — exact color value, spacing, node structure — must be resolved by opening the.penfile and querying viabatch_getwithresolveVariables: true. The live file takes precedence over any saved artifact.
Inputs (provided by design-extractor)
mode:PANORAMIC|SURGICAL|COMPONENT_MAPfilePath(SURGICAL + COMPONENT_MAP): absolute or relative path to the.penfilesectionId(SURGICAL, optional): Pencil node ID of the section to extractsectionName(SURGICAL, optional): name of the section — used to resolvesectionIdif not providedplanPath(optional): path to the active plan directory — used for saving assets
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 · 339 lines · 61 tokens per session scan A 598ae1011df0
superpowers-sage:pencil-extractor is an agent published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 3,333 once invoked, about $0.0003 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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
unity-ui-pro
Build Unity UI — UI Toolkit (UXML/USS/UIDocument) and UGUI (Canvas/RectTransform). Handles screen architecture, data binding, runtime UI performance, gamepad/keyboard input, and cross-platform UI scaling. Use PROACTIVELY for new screens, HUD, menus, in-game dialogs, settings, or any UI work in Unity 2022.3+. Not for…