prep

prep is a skill for Claude Code from byjunyoung/claude-product-skills. It costs 154 tokens per session (4,417 once invoked), scanned A, original, no licence file.

A Figma preparation workflow that organizes a design page by renaming frames, adding feature sections, and creating placeholders for missing screen states or interaction results.

In plain words
What is it for?
Use it to prepare Figma screens, normalize frame names, and stub missing states before designing them fully.
Why use it?
It exposes unrepresented cases before the main design work begins, so the page covers more of the intended experience.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the fig plugin — 14 skills, 1 hook shipped together

Good fit Use it to prepare Figma screens, normalize frame names, and stub missing states before designing them fully.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/byjunyoung/claude-product-skills/prep
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 byjunyoung/claude-product-skills --skill prep
Clone the repo
git clone --depth 1 https://github.com/byjunyoung/claude-product-skills

Made for: Claude Code.

Or install fig, the plugin that ships this one along with the rest of its 14 skills, 1 hook.

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 prep

README.md
[![agentmods](https://agentmods.dev/badge/skills/byjunyoung/claude-product-skills/prep/github.svg)](https://agentmods.dev/skills/byjunyoung/claude-product-skills/prep)
Your own site
<a href="https://agentmods.dev/skills/byjunyoung/claude-product-skills/prep"><img src="https://agentmods.dev/badge/skills/byjunyoung/claude-product-skills/prep/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 prep

Your own site · 80×15
<a href="https://agentmods.dev/skills/byjunyoung/claude-product-skills/prep"><img src="https://agentmods.dev/badge/skills/byjunyoung/claude-product-skills/prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,417 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 unknown 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.00154 $0.04417
Opus 5 $0.00077 $0.02209
Sonnet 5 $0.00031 $0.00883
Haiku 4.5 $0.00015 $0.00442

Measured 6d ago against content hash fc46240cbc97, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

prep 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 6d 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.

plugins/fig/skills/prep/SKILL.md · 197 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 6d ago Changed · +2 lines fc46240cbc97
  2. 10d ago First seen · 195 lines · 154 tokens per session scan A b347d43f315f

Subscribe to this mod's changes

prep is a skill published in the GitHub repository byjunyoung/claude-product-skills (5 stars, last pushed 2d ago), with no licence file. It adds 154 tokens to every session and 4,417 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

system-pitch

Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…

murphytrueman/design-system-ops · 72 tokens

stakeholder-brief

Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…

murphytrueman/design-system-ops · 73 tokens

token-audit

Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…

murphytrueman/design-system-ops · 93 tokens

accessibility-per-component

Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…

murphytrueman/design-system-ops · 65 tokens

ai-component-description

Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…

murphytrueman/design-system-ops · 132 tokens

context-engine-builder

Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…

murphytrueman/design-system-ops · 135 tokens