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 swift-package-testing-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/swift-package-testing-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/swift-package-testing-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/swift-package-testing-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/swift-package-testing-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/swift-package-testing-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.00077 | $0.02201 |
| Opus 5.5 | $0.00031 | $0.00880 |
| Sonnet 5.5 | $0.00015 | $0.00440 |
| Haiku 4.5 | $0.00008 | $0.00220 |
Grade A, and why
swift-package-testing-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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift Package Testing Workflow
Purpose
Use this skill as the primary execution workflow for test-focused work in existing Swift package components. Keep it focused on Swift Testing, XCTest holdouts, code coverage, .xctestplan handoff conditions, async-test guidance, semantic accessibility-test boundaries, performance-sensitive package workload profiling, filters, retries, fixtures, and package-level test diagnosis. scripts/run-workflow.fsx resolves the nearest package root and plans the test surface without classifying the containing repository.
When To Use
- Use this skill for running, diagnosing, organizing, or evolving tests in an existing Swift package repo.
- Use this skill for Swift Testing-first package work, XCTest holdouts, async-test design, semantic accessibility-test boundaries, and test-fixture organization.
- Use this skill for package-level
.xctestplanexecution when the package surface needs Xcode test-plan follow-through. - Use this skill when the request is about test selection, filtering, retries, failures, flaky tests, or test-only Debug/Release validation.
- Use this skill when the request is about package-first performance-sensitive testing, signpost placement, Release workload harnesses, or profiling-ready package test design for Audio, Metal, MLX, local AI, streaming, or other Apple silicon-sensitive workloads.
- Do not use this skill for broad manifest edits, dependency work, package resources, package-extension design, or ordinary build and run work.
- Do not use this skill for brand-new package bootstrap from nothing.
- Do not use this skill for repo-guidance alignment in an existing package repo.
- Do not use this skill as the default path for Xcode workspace, scheme, preview, simulator, or navigator-driven work.
- Recommend
swift-package-build-run-workflowwhen the request is primarily about ordinary package build/run, manifest, dependency, resource, or Metal-distribution work. - Recommend
swift-package-extension-workflowwhen trait matrices, macro/plugin test shape, or generated-source validation is the primary concern. - Recommend
bootstrap-xcode-workspace --operation create --component-kind librarywhen the package repo does not exist yet. - Recommend root workspace
just alignwhen product guidance needs to be refreshed. - Recommend
xcode-testing-workflowwhen test work depends on active Xcode workspace state, navigator diagnostics, simulator or device flows, XCUITest, runtime accessibility verification, or Xcode-native test plans and test execution. - Recommend
apple-ui-accessibility-workflowwhen the request is primarily about accessibility semantics or review rather than package-side testing strategy. - Recommend
xcode-build-run-workflowwhen package test work crosses into guarded mutation, file membership, or other Xcode-managed project-integrity work. - Recommend
explore-apple-swift-docswhen the user needs Apple or Swift docs exploration before implementation or test changes.
What ships with it
8 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.
- agents/openai.yaml 507 B
- references/cli-command-matrix.md 2.2 KB
- references/code-coverage.md 1.7 KB
- references/package-resources-testing-and-builds.md 4.5 KB
- references/performance-sensitive-testing-and-profiling.md 9.4 KB
- references/snippets/apple-swift-package-core.md 15 KB
- references/workflow-policy.md 773 B
- scripts/run-workflow.fsx 3.3 KB
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 · 138 lines · 77 tokens per session scan A d5ee89478b26
swift-package-testing-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 2,201 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-09-03.
Other skills, from other repositories
completion-verification
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of…
execute
Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.
browser-agent
Autonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.
tdd
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.
verify
Fresh verification gate before claiming done, fixed, passing, ready, or before commit/PR. Evidence before claims, always.
integration
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.