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/tvos-app-experience-workflownpx skills add gaelic-ghost/socket --skill tvos-app-experience-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/tvos-app-experience-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/tvos-app-experience-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/tvos-app-experience-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.00053 | $0.01590 |
| Opus 5 | $0.00026 | $0.00795 |
| Sonnet 5 | $0.00011 | $0.00318 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
tvos-app-experience-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 yesterday.
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tvOS App Experience Workflow
Purpose
Guide the Apple TV-specific decisions that ordinary SwiftUI app architecture does not own: indirect remote/controller input, visible focus movement, large-screen layout, Large Text, hardware and SDK availability, and migration away from TVMLKit. Keep SwiftUI as the primary UI path and use UIKit focus APIs only for a demonstrated geometry or lifecycle constraint.
When To Use
- Use this skill for a tvOS catalog, utility, education, fitness, game-adjacent, or media-browsing app whose main question is remote-first interaction or focus behavior.
- Use this skill for SwiftUI content shelves, lockups, hover effects,
focusSection(), focused-item clipping, focus restoration, or large-screen layout decisions. - Use this skill for
UIFocusGuide,UIFocusEnvironment, preferred focus environments, focus-update diagnostics, or a UIKit/SwiftUI focus boundary. - Use this skill for tvOS 27 Large Text/Dynamic Type adaptation, remote versus controller input, text-entry burden, Apple TV hardware/GPU capability gates, and beta-SDK availability questions.
- Use this skill to inventory a TVMLKit app and plan a migration to SwiftUI or UIKit; TVMLKit has been deprecated since tvOS 18.
- Recommend
tvos-media-playback-workflowwhen playback UI, remote transport commands, Now Playing state, AVKit customization, HLS, or a custom player is the primary concern. - Recommend
swiftui-app-architecture-workflowwhen the tvOS constraints are understood and the remaining question is ordinary SwiftUI scene, state, or component ownership. - Recommend
apple-ui-accessibility-workflowwhen the main question is the accessibility tree or semantics beyond tvOS focus and Large Text.
Single-Path Workflow
- Classify the request:
- SwiftUI-first content layout
- focus routing or restoration
- UIKit focus escape hatch
- Large Text or accessibility adaptation
- capability or beta-SDK gate
- TVMLKit migration inventory
- Apply the Apple docs gate:
- use
explore-apple-swift-docsto read current Apple documentation first - state the documented focus, input, availability, or deprecation behavior relied on before proposing a change
- mark tvOS 27 claims as beta-specific with the checked SDK/build date until Apple ships the GM
- use
- Choose the smallest native UI surface:
- SwiftUI
Button,focusSection(), lockup, hover-effect, and scroll behavior for normal catalog layouts - normal focus geometry with enough room for scale and elevation
- UIKit
UIFocusGuideor preferred focus environments only when native geometry cannot produce the intended movement
- SwiftUI
- Check the platform boundary:
- Siri Remote, controller, voice, or companion-device input
- focus, select, Menu/Back, and restoration behavior
- text-entry alternative and remote friction
- Apple TV generation, GPU family, simulator/device-only requirement, and unavailable framework
- Large Text, RTL, VoiceOver order, and visual focus states
- Return one recommendation with:
- resolved request class
- documented Apple behavior relied on
- selected SwiftUI or UIKit surface
- platform/beta availability result
- validation matrix and one honest 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.
- yesterday First seen · 157 lines · 53 tokens per session scan A 1ddcbc0dc1e6
tvos-app-experience-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,590 once invoked, about $0.0003 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
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…
scenario-planning
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…
ai-ml-governance
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…
ai-research-analyst
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a…
implement-factory
Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.