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 operate-zed-agentgit 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/operate-zed-agent)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/operate-zed-agent"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/operate-zed-agent/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/operate-zed-agent"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/operate-zed-agent.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.00042 | $0.00937 |
| Opus 5.5 | $0.00017 | $0.00375 |
| Sonnet 5.5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
operate-zed-agent 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate Zed Agent
Choose the Zed agent path before editing settings. Read
references/zed-surface-map.md when the request crosses native and external
agent configuration.
Choose the Agent Path
- Use Zed Agent when Zed should own the model, provider, tools, profiles, permissions, instructions, skills, and MCP configuration.
- Use an External Agent when an ACP agent such as Codex, Claude, OpenCode, or Hermes should own its runtime, model, authentication, native skills, and persistent state while Zed owns the editor UI.
- Use a Terminal Thread when the original CLI or TUI behavior matters more than ACP-native diffs, approvals, or session rendering.
Do not apply Zed Agent Skills or profiles to an External Agent by assumption. The external agent keeps its own configuration unless its ACP implementation explicitly accepts a forwarded capability.
Configure Zed Agent
- Confirm the worktree is trusted before expecting project-local skills.
- Use Zed's Skills Manager to create or import a skill when interactive management is appropriate. A GitHub URL import is an installation copy, not a remote runtime dependency.
- Keep manually managed skills as direct children of global
~/.agents/skills/or project.agents/skills/; Zed does not discover nested or arbitrary search roots. - Keep names and descriptions concise because Zed has a catalog budget.
- Use
/skillor@skillfor explicit invocation. Usedisable-model-invocationonly when the skill must never be selected implicitly. - Treat
zed://skilllinks as sharing/import affordances, not proof of a centrally hosted runtime registry. - Use Zed Instructions for always-on guidance, Agent Profiles for tool selection, Tool Permissions for approval policy, and Zed MCP configuration for external tools.
- Expect installed skill changes to reload without restarting, then verify the catalog entry and one harmless invocation.
Configure an External Agent
- Check the live canonical ACP Registry instead of trusting a product page or an agent's source manifest.
- Prefer the registry only when the requested agent is actually present.
- Otherwise add a custom
agent_serversentry using the agent's official executable and arguments. Do not substitute an unreviewed third-party launcher merely to make a registry row appear. - Configure provider credentials and native agent state in the external agent unless its integration documents another owner.
- Start a new thread and verify the agent identity, working directory, model, skills, MCP tools, and approval behavior.
- Use
dev: open acp logsto inspect Zed-to-agent protocol traffic.
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.
- 1mo ago First seen · 91 lines · 42 tokens per session scan A 453b29bf9c6f
operate-zed-agent is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 937 once invoked, about $0.0002 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
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…
pipeline-auto
Use when the user wants a substantial feature taken from idea through implementation in one run with as little interruption as possible ("just build it", "don't keep asking me"), or when controlling such a run and a worker question, quorum responses, the drift budget, a human decision, a review class or a completeness…
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.
fast-pipeline
Use when the user wants a feature built quickly with low token cost and few interruptions, approves a spec once, and says no automated tests should be written because they will test it manually — "fast pipeline", "go fast, no tests, I'll test it myself", "don't keep asking me". Not for a run that should write or keep…