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 author-swift-docc-docsgit 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/author-swift-docc-docs)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/author-swift-docc-docs"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/author-swift-docc-docs/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/author-swift-docc-docs"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/author-swift-docc-docs.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.00070 | $0.01321 |
| Opus 5.5 | $0.00028 | $0.00528 |
| Sonnet 5.5 | $0.00014 | $0.00264 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
author-swift-docc-docs 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Author Swift DocC Docs
Purpose
Provide the canonical DocC authoring-and-review workflow for Swift components. scripts/run-workflow.fsx classifies the task and, only when execution is needed, selects SwiftPM or Xcode according to the requested generation operation.
When To Use
- Use this skill for in-source symbol documentation work that is meant to compile into DocC output.
- Use this skill for DocC article writing and review.
- Use this skill for DocC extension-file, landing-page, topic-group, and catalog-structure work.
- Use this skill when the user wants a DocC-oriented review pass for clarity, content accuracy, or DocC-specific structure quality.
- Use this skill when the user wants help deciding whether content belongs in source comments, articles, extension files, or landing pages.
- Use this skill for tutorial-aware DocC review when the user clearly wants DocC tutorial help but the task is still mainly about authoring shape and conceptual flow rather than directive-deep mechanics.
- Recommend
explore-apple-swift-docswhen the user really needs broader Apple or Swift documentation lookup, WWDC-material lookup, or directive-reference lookup instead of DocC authoring or review work. - Recommend
swift-package-build-run-workflowfor SwiftPM DocC generation and package-oriented follow-through. - Recommend
xcode-build-run-workflowforProduct > Build Documentation,xcodebuild docbuild, scheme, export, archive, or project-integrity follow-through.
Single-Path Workflow
- Classify the DocC task:
symbol-docsarticlestructurereviewtutorial-aware-review
- Run
scripts/run-workflow.fsxso task inference, tutorial-depth boundaries, and handoff rules resolve into one JSON contract. - If the request is actually broad Apple-docs lookup, hand off to
explore-apple-swift-docs. - If the request is DocC generation, export, hosting, archive, or project-integrity follow-through, select the execution surface required by that operation and hand off to its owner.
- Otherwise stay local to DocC authoring and review:
- revise or review source comments
- revise or review articles and extension files
- review landing-page and topic-group structure
- explain the difference between content correctness, DocC correctness, and project correctness
- Return one
status, onepath_type, one resolved task type, optional execution surface, and one next-step contract.
What ships with it
7 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 · 110 lines · 70 tokens per session scan A 248f18d3db0c
author-swift-docc-docs is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,321 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
kotlin-dev
Use when implementing any feature or bugfix in a Kotlin/Spring Boot service, covers layer conventions, idioms, testing, and observability.
kotlin-reviewer
Use when reviewing a Kotlin/Spring Boot pull request, systematic checklist covering architecture, idioms, testing, security, and observability.
swiftui-macos
Expert SwiftUI guidance for macOS apps — covers writing and reviewing code with runtime-level understanding of observation, concurrency, performance, and platform integration. Use when user asks to "build a SwiftUI view", "review my SwiftUI code", "fix observation issues", "bridge AppKit", "architect state…
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.
turbo-pipeline
Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…