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/gaelic-ghost/socket/sf-symbols-workflownpx skills add gaelic-ghost/socket --skill sf-symbols-workflowgit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/sf-symbols-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/sf-symbols-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/sf-symbols-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.00109 | $0.02006 |
| Opus 5 | $0.00055 | $0.01003 |
| Sonnet 5 | $0.00022 | $0.00401 |
| Haiku 4.5 | $0.00011 | $0.00201 |
Grade A, and why
sf-symbols-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 2d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SF Symbols Workflow
Purpose
Use this skill to choose, inspect, customize, validate, and integrate SF Symbols in Apple app UI. The skill owns symbol selection, SF Symbols app inspection, rendering-mode decisions, custom-symbol workflow, symbol animation routing, and accessibility semantics.
It is not the app-icon workflow, not the generic SwiftUI animation workflow, and not the Xcode project execution workflow.
When To Use
- Use this skill when the user asks about Apple's SF Symbols library or SF Symbols app.
- Use this skill when the task mentions built-in symbols,
Image(systemName:),Label,UIImage(systemName:),NSImage(systemSymbolName:),symbolRenderingMode,symbolVariant,foregroundStyle,variableValue,symbolEffect,SymbolEffectTransition, custom symbols, or symbol templates. - Use this skill when a UI design needs a semantically correct icon, state variant, platform-available symbol, palette/multicolor rendering, variable color, or animated symbol effect.
- Use this skill when the user wants Codex to inspect the local SF Symbols app through Computer Use.
- Recommend
swiftui-animation-workflowwhen the primary question is broader SwiftUI motion, transition design, state-driven animation, phase animation, keyframe animation, or reduce-motion behavior. - Recommend
icon-composer-app-icon-workflowwhen the work is an app icon rather than an in-app symbol. - Recommend
apple-ui-accessibility-workflowwhen the main issue is accessibility review beyond symbol labels and semantic meaning. - Recommend
xcode-build-run-workflowwhen the next honest step is asset-catalog integration, build, preview, simulator, or project-file validation.
Single-Path Workflow
- Classify the symbol job:
- choose a built-in symbol
- repair an incorrect or unavailable symbol name
- choose a variant, such as fill, slash, circle, square, or badge
- choose monochrome, hierarchical, palette, or multicolor rendering
- apply variable color or variable draw behavior
- apply a symbol effect or symbol transition
- create, annotate, validate, or export a custom symbol
- integrate an asset-catalog symbol into an app
- Apply the Apple docs gate:
- read the relevant Apple documentation first
- state the documented behavior being relied on before recommending implementation
- if Apple docs and the local SF Symbols app disagree, stop and surface the conflict
- if no relevant Apple docs can be found, say that explicitly before proceeding
- Inspect the local tool when current symbol-library behavior matters:
- verify the SF Symbols app exists before promising GUI guidance
- inspect the local app through Computer Use when the task needs category, rendering, animation, export, or custom-symbol evidence
- use the app's sidebar and inspectors to verify symbol availability, variants, rendering support, variable behavior, and animation support
- Choose the symbol path:
- built-in SF Symbol when the semantic match and platform availability are good
- built-in symbol plus variant when the state is a standard variant
- rendering-mode or palette change when the shape is right and only color semantics need work
- symbol effect when the motion is symbol-local and Apple documents the effect for the target platforms
- custom symbol when the app needs a brand-specific or unavailable symbol while preserving SF Symbols metrics and template rules
- ordinary SVG/vector artwork when the shape is not a symbol and does not benefit from SF Symbols behavior
- Check implementation boundaries:
- SwiftUI uses
Image,Label, symbol modifiers,foregroundStyle,symbolEffect, and asset names when appropriate - UIKit and AppKit use image and symbol configuration APIs when appropriate
- Xcode project and asset-catalog changes hand off to
xcode-build-run-workflow - app-icon work hands off to
icon-composer-app-icon-workflow
- SwiftUI uses
- Return one recommendation path with:
- the symbol source
- rendering and animation choices
- accessibility semantics
- documentation behavior relied on
- validation or handoff steps
What ships with it
4 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.
- 2d ago First seen · 144 lines · 109 tokens per session scan A d43b9637148d
sf-symbols-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 109 tokens to every session and 2,006 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
app-store-optimization
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
flutter-dart-code-review
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
pipeline
Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.