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 contain-and-recover-macosgit 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/contain-and-recover-macos)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/contain-and-recover-macos"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/contain-and-recover-macos/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/contain-and-recover-macos"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/contain-and-recover-macos.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.00047 | $0.00480 |
| Opus 5 | $0.00023 | $0.00240 |
| Sonnet 5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
contain-and-recover-macos 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 5d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contain And Recover macOS
Overview
Choose actions proportionate to evidence and ongoing harm. Preserve what matters, use official lifecycle controls, and verify the system after eradication rather than declaring it clean because one artifact disappeared.
Read references/macos-response-ladder.md for containment and recovery levels.
Workflow
- Confirm assessment, confidence, affected scope, ongoing behavior, critical data, and evidence needs.
- Choose immediate containment.
- Prefer reversible network/account/session isolation when it stops harm.
- Record the effect on volatile evidence and business/user access.
- Preserve decisive evidence.
- Capture artifact, persistence, process/network/log, account, and timeline records before removal when delay is safe.
- Stop active behavior through official controls.
- End processes/services deliberately; use
launchctl bootoutfor approved launch service removal from a domain, app-provided uninstallers for app components, and supported profile/extension management surfaces. - Never edit launchd's internal state directly.
- End processes/services deliberately; use
- Eradicate the verified mechanism.
- Remove or quarantine confirmed artifacts, registrations, extensions, profiles, helpers, rules, and downloaded stages; preserve hashes and paths.
- Do not reset, disable, or weaken TCC, Gatekeeper, XProtect, SIP, App Sandbox, or another protection merely to make a suspicious artifact run or simplify removal.
- Respond to identity exposure.
- Rotate affected credentials/tokens from a trusted device, revoke sessions/keys, review MFA and recovery methods, and notify owners/providers as warranted.
- Recover.
- Restore from a known-good point, reinstall/erase when integrity cannot be established, apply updates, reconfigure only needed access, and avoid restoring suspect persistence.
- Verify and monitor.
- Recheck persistence, runtime/network, accounts, security updates, backups, and recurrence across a defined observation window.
What ships with it
2 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.
- 5d ago First seen · 38 lines · 47 tokens per session scan A b6a5bf9b5696
contain-and-recover-macos is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 13d ago), licensed Apache-2.0. It adds 47 tokens to every session and 480 once invoked, about $0.0002 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…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
setup
Use when superb's skills need their dependencies installed or checked — "set up superb", "install the dependencies", "why does pipeline say superpowers is missing", after a fresh plugin install, or on a new machine. Also use when a skill fails complaining that a superpowers sub-skill cannot be found.
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…