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 gaelic-ghost/socket --skill core-image-processing-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/core-image-processing-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/core-image-processing-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/core-image-processing-workflow/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/gaelic-ghost/socket/core-image-processing-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/core-image-processing-workflow.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.00074 | $0.01318 |
| Opus 5.5 | $0.00030 | $0.00527 |
| Sonnet 5.5 | $0.00015 | $0.00264 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
core-image-processing-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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Image Processing Workflow
Purpose
Guide Core Image processing and rendering without turning CIImage into a bitmap wrapper or mixing transformation with file decoding, visual recognition, or display-container ownership. Preserve Core Image, Core Graphics, Core Video, and Metal types until an explicit output boundary.
When To Use
- Use for Core Image filter chains, compositing, RAW development, custom kernels, color or HDR processing, render destinations, and Core Image performance or correctness repair.
- Recommend
apple-image-representation-workflowwhen decoding, encoding, metadata, or platform image-container behavior is primary. - Recommend the Vision workflow when the requested outcome is recognition or analysis rather than pixel transformation.
Single-Path Workflow
- Classify the request:
- built-in filter chain
- compositing, masking, scaling, or geometry
- RAW development
- custom kernel or processor
- color, HDR, or alpha repair
- render destination or interop
- performance or correctness diagnosis
- Apply the Apple docs gate:
- read current Core Image documentation before proposing implementation changes
- state the documented behavior relied on
- apply
../../shared/references/apple-image-type-ownership.md - use
references/core-image-processing-and-rendering.mdfor graph, context, color, render, and performance decisions - use
references/core-image-diagnostics-and-handoffs.mdfor repair probes and ownership handoffs
- Define the graph and ownership:
- identify the source image, extent, orientation state, color space, alpha semantics, and dynamic range
- build immutable
CIImagetransformations and keep mutableCIFilterinstances task-local - choose one deliberately scoped, reusable
CIContext - select the output bounds, format, color space, and destination before rendering
- Repair common failure modes:
- treating
CIImageas already-rendered pixels - creating a new
CIContextper frame or filter application - sharing mutable
CIFilterinstances across concurrent work - losing orientation, extent, alpha, color-space, HDR, or auxiliary-data meaning during conversion
- forcing CPU readback between Core Image, Core Video, and Metal without a concrete boundary
- rendering infinite or unexpectedly expanded extents without an explicit crop
- using Core Image as a recognition framework instead of handing analysis to Vision
- treating
- Return one recommendation with:
- processing class and documented behavior
- source and output type ownership
- graph, context, color, extent, and render-destination plan
- concurrency, cancellation, memory, and performance plan
- repair findings and runtime validation handoff
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.
- 1mo ago First seen · 100 lines · 74 tokens per session scan A 665df2414e2c
core-image-processing-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,318 once invoked, about $0.0003 per session on Opus 5.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.
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-screenshots
Automate App Store & Google Play screenshot generation for Flutter apps. Scans routing and screens, scores high-value marketing screens, generates self-contained mock harness, runs native simulator captures (iPhone 6.9", iPad 13", Android Phone/Tablet), strips alpha channels, and validates exact store resolutions.
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.
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…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.