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 madebypan/FigCC --skill favicon-exportergit clone --depth 1 https://github.com/madebypan/FigCCWrote 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/madebypan/figcc/favicon-exporter)<a href="https://agentmods.dev/skills/madebypan/figcc/favicon-exporter"><img src="https://agentmods.dev/badge/skills/madebypan/figcc/favicon-exporter.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.01487 |
| Opus 5 | $0.00010 | $0.00744 |
| Sonnet 5 | $0.00004 | $0.00297 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
favicon-exporter 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Favicon Exporter
You are an expert at setting up favicon export configurations in Figma. When the user asks to create favicon assets, export favicons, or set up a favicon from a selected icon, follow these patterns.
What this does
- Takes the currently selected node as the source icon
- Adds the correct export settings (sizes + formats) directly on the node
- Shows the user an HTML
<head>snippet they can copy-paste into their website - The user then manually exports the files from Figma's Export panel (File → Export or the Export section in the right panel)
Required favicon exports
File names use the node's name as the prefix (e.g. node fav → fav-16x16.png).
| File name pattern | Format | Size |
|---|---|---|
<name>.svg |
SVG | Vector (scalable) |
<name>-16x16.png |
PNG | 16×16 |
<name>-32x32.png |
PNG | 32×32 |
<name>-180x180.png |
PNG | 180×180 (Apple touch icon) |
<name>-192x192.png |
PNG | 192×192 |
<name>-512x512.png |
PNG | 512×512 |
Setting export settings on the selected node
Use exportSettings to configure all required sizes at once. Figma uses constraint with type: 'WIDTH' or type: 'HEIGHT' to scale exports.
const node = figma.currentPage.selection[0];
if (!node) return { error: 'No node selected. Please select the icon first.' };
const name = node.name.toLowerCase().replace(/\s+/g, '-');
node.exportSettings = [
{ format: 'SVG' },
{ format: 'PNG', constraint: { type: 'WIDTH', value: 16 }, suffix: '-16x16' },
{ format: 'PNG', constraint: { type: 'WIDTH', value: 32 }, suffix: '-32x32' },
{ format: 'PNG', constraint: { type: 'WIDTH', value: 180 }, suffix: '-180x180' },
{ format: 'PNG', constraint: { type: 'WIDTH', value: 192 }, suffix: '-192x192' },
{ format: 'PNG', constraint: { type: 'WIDTH', value: 512 }, suffix: '-512x512' },
];
return {
node: node.name,
name: name,
exportSettingsAdded: node.exportSettings.length,
};
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 · 118 lines · 19 tokens per session scan A 55cd11783ccf
favicon-exporter is a skill published in the GitHub repository madebypan/FigCC (22 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 1,487 once invoked, about $0.0001 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
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage…
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
refero-design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this…
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
frontend-specialist
A front-end development workflow for building or improving web pages, components, layouts, forms, dashboards, and responsive interfaces. It covers common tools and frameworks such as React, Vue, Next.js, Tailwind, and CSS.