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/assess-macos-threatnpx skills add gaelic-ghost/socket --skill assess-macos-threatgit 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/assess-macos-threat)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/assess-macos-threat"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/assess-macos-threat.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.00046 | $0.00573 |
| Opus 5 | $0.00023 | $0.00287 |
| Sonnet 5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
assess-macos-threat 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess macOS Threat
Overview
Establish the affected Mac and event timeline before changing the system. Use Apple security layers as separate evidence sources and route focused persistence, runtime, artifact, or containment work from the resulting record.
Read references/macos-security-layers.md when interpreting platform controls or alerts.
Workflow
- Identify the Mac and event.
- Record model/chip, exact macOS build, update state, user/session, time/timezone, managed-device context, and what the person observed.
- Record whether evidence comes from the affected physical host, a macOS guest, or a reproduction guest. For guest evidence, include the VM framework/tool, virtual hardware, restore image, integrations, baseline/reset state, and anti-VM or hardware fidelity limits.
- Preserve the triggering evidence.
- Record alert text/screenshots, file path/source/hash, quarantine metadata, process identity, prompts, downloads, and relevant logs before cleanup.
- Inspect artifact identity.
- Record real type, bundle/package metadata, signer, Team ID, signature verification, notarization assessment, entitlements, modifications, and source channel.
- Route binary internals to Reverse Engineering Skills.
- Inspect platform evidence.
- Check Gatekeeper/quarantine context, XProtect detections or remediation evidence, TCC/privacy grants, SIP state, profiles, login/background items, system extensions, and relevant system policy without disabling protections.
- Correlate behavior.
- Route process/file/network evidence to runtime inspection and startup/registration clues to persistence inspection.
- Separate a blocked attempt from successful execution and successful execution from compromise.
- Assess and advise.
- State classification/confidence, immediate isolation needs, evidence gaps, and the smallest next workflow.
- Route ordinary application permission implementation to
macos-privacy-permissions-workflow; route private symbols, control internals, or exact-build Gatekeeper/XProtect/TCC questions toresearch-macos-security-control. - Do not generalize guest-observed behavior to a physical Mac when hardware, Secure Enclave, recoveryOS, kernel/system-extension, device, or anti-VM behavior remains unresolved.
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.
- yesterday First seen · 39 lines · 46 tokens per session scan A bd8ead237929
assess-macos-threat is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 46 tokens to every session and 573 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…
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…
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
business-growth-consultant
Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when…
ceo-advisor
Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check…