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 skills add Hipson47/Hipson --skill figma-create-new-filegit clone --depth 1 https://github.com/Hipson47/HipsonWrote 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/hipson47/hipson/figma-create-new-file)<a href="https://agentmods.dev/skills/hipson47/hipson/figma-create-new-file"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/figma-create-new-file/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/skills/hipson47/hipson/figma-create-new-file"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/figma-create-new-file.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.00085 | $0.00715 |
| Opus 5 | $0.00043 | $0.00358 |
| Sonnet 5 | $0.00017 | $0.00143 |
| Haiku 4.5 | $0.00009 | $0.00072 |
Grade A, and why
figma-create-new-file 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.
This is a copy
91% identical to figma-create-new-file — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create_new_file — Create a New Figma File
Use the create_new_file MCP tool to create a new blank Figma file in the user's drafts folder. This is typically used before use_figma when you need a fresh file to work with.
Skill Arguments
This skill accepts optional arguments: /figma-create-new-file [editorType] [fileName]
- editorType:
design(default) orfigjam - fileName: Name for the new file (defaults to "Untitled")
Examples:
/figma-create-new-file— creates a design file named "Untitled"/figma-create-new-file figjam My Whiteboard— creates a FigJam file named "My Whiteboard"/figma-create-new-file design My New Design— creates a design file named "My New Design"
Parse the arguments from the skill invocation. If editorType is not provided, default to "design". If fileName is not provided, default to "Untitled".
Workflow
Step 1: Resolve the planKey
The create_new_file tool requires a planKey parameter. Follow this decision tree:
-
User already provided a planKey (e.g. from a previous
whoamicall or in their prompt) → use it directly, skip to Step 2. -
No planKey available → call the
whoamitool. The response contains aplansarray. Each plan has akey,name,seat, andtier.- Single plan: use its
keyfield automatically. - Multiple plans: ask the user which team or organization they want to create the file in, then use the corresponding plan's
key.
- Single plan: use its
Step 2: Call create_new_file
Call the create_new_file tool with:
| Parameter | Required | Description |
|---|---|---|
planKey |
Yes | The plan key from Step 1 |
fileName |
Yes | Name for the new file |
editorType |
Yes | "design" or "figjam" |
Example:
{
"planKey": "team:123456",
"fileName": "My New Design",
"editorType": "design"
}
Step 3: Use the result
The tool returns:
file_key— the key of the newly created filefile_url— a direct URL to open the file in Figma
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 69 lines · 85 tokens per session scan A 23f429203bd5
figma-create-new-file is a skill published in the GitHub repository Hipson47/Hipson (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 715 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to figma-create-new-file, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
kirby-panel-and-blueprints
Designs Kirby blueprints and Panel UI, including blueprint reuse/extends, programmable blueprints, and custom Panel fields/sections/areas. Use when changing the Panel experience or schema.
bootstrap-design
A guided process for choosing a user interface’s visual direction and recording the decisions in DESIGN.md.
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.
agent-support-matrix
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility. Use when checking upstream agent releases for session format changes, updating max verified versions in docs/agent-support/agent-support-matrix.yml, or updating docs/agent-json-tracking.md and fixtures/tests.
diagrams
Mermaid diagrams following the C4 model: context, container, component, sequence, ER and deployment. Use when saying "diagram", "visualize", or "architecture diagram".
from-intake
A workflow for reviewing material brought from another workspace and carrying relevant brand evidence into the project's assets. It checks inventories, brand guides, logos, and image sources before anything is used.