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 camera-capture-depth-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/camera-capture-depth-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/camera-capture-depth-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/camera-capture-depth-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/camera-capture-depth-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/camera-capture-depth-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.00087 | $0.01428 |
| Opus 5.5 | $0.00035 | $0.00571 |
| Sonnet 5.5 | $0.00017 | $0.00286 |
| Haiku 4.5 | $0.00009 | $0.00143 |
Grade A, and why
camera-capture-depth-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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Camera Capture and Depth Workflow
Purpose
Guide AVFoundation camera, photo, depth, and computational-capture work while keeping general session topology, media pipelines, sample timing, audio policy, Vision analysis, and ARKit spatial sensing with their owning workflows.
When To Use
- Use for camera discovery, formats, controls, rotation, photo features, depth, calibration, synchronized outputs, mattes, pressure, and device-specific capture repair.
- Recommend
avfoundation-media-pipeline-workflowwhen general capture-session, output queue, player, asset, reader, writer, export, or back-pressure ownership is primary. - Recommend
vision-image-analysis-workflowwhen capture is working and image interpretation is the actual task.
Single-Path Workflow
- Classify the request:
- device discovery or selection
- format, frame rate, MultiCam, or constituent device
- focus, exposure, white balance, zoom, torch, stabilization, or low light
- rotation, orientation, or mirroring
- processed, RAW, bracketed, Live Photo, responsive, or deferred photo capture
- depth, disparity, calibration, or synchronized output
- portrait-effects, semantic, spatial, or cinematic capture
- authorization, interruption, pressure, dropped data, or runtime repair
- Apply the Apple docs gate:
- read current AVFoundation documentation for every requested feature and platform
- state the documented behavior relied on
- apply
../../shared/references/apple-camera-capability-contract.md - apply
../../shared/references/apple-media-type-ownership.md
- Discover before configuration:
- use
AVCaptureDevice.DiscoverySession, available devices, virtual-device constituents,AVCaptureDevice.Format, supported frame-rate ranges, depth formats, session support, output support, and connection support - never infer capability from a marketing device name, lens count, or OS version alone
- use
- Configure through one owner:
- keep session graph mutation on the serial session owner defined by
avfoundation-media-pipeline-workflow - balance
lockForConfiguration()andunlockForConfiguration()and mutate only supported device properties - configure output, settings, connection, rotation, mirroring, and delegate lifecycle explicitly
- keep session graph mutation on the serial session owner defined by
- Preserve typed capture data:
- keep
AVCapturePhoto,AVDepthData,AVCameraCalibrationData,AVPortraitEffectsMatte,AVSemanticSegmentationMatte,CMSampleBuffer, synchronized data, and dropped-data reasons inspectable - record timestamps, dimensions, orientation, pixel/depth formats, calibration, filtering, accuracy, and source identity
- keep
- Validate honestly:
- distinguish documented support, discovered runtime support, simulator limitations, and physically verified behavior
- return the capability evidence, configuration, output lifecycle, pressure/error policy, diagnostics, and device validation plan
What ships with it
5 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 · 95 lines · 87 tokens per session scan A ed4e295869eb
camera-capture-depth-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,428 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.