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-acp-agent-integrationgit 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-acp-agent-integration)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/operate-acp-agent-integration"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/operate-acp-agent-integration/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-acp-agent-integration"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/operate-acp-agent-integration.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.00847 |
| Opus 5.5 | $0.00019 | $0.00339 |
| Sonnet 5.5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
operate-acp-agent-integration 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate ACP Agent Integration
Operate an existing ACP agent without confusing client setup, agent-native
configuration, and protocol behavior. Read references/acp-operations-map.md
for the current connection and failure map.
Preflight
- Name the ACP client and ACP agent/server process.
- Treat ACP v1 as the current latest protocol and v2 as draft design work. Check the capabilities negotiated by the actual pair; do not infer wire compatibility from SDK package versions or implement a draft RFD as stable.
- Check the canonical ACP Registry with the managed ACP registry checker.
- If the agent is missing, use its official local executable only when the client supports custom agents. Keep registry absence distinct from missing ACP support.
- Run the agent's documented non-interactive health or version check before opening the client.
For Hermes, check hermes acp --version, hermes acp --check, hermes doctor,
and hermes status as needed. ACP reuses Hermes provider credentials, config,
skills, and state; it does not create a separate provider setup.
Connect And Validate
- Configure the client launch command and environment with the smallest required surface.
- Confirm stdout is reserved for JSON-RPC and human-readable logs go to stderr.
- Inspect the initialization response for protocol version, agent capabilities, authentication methods, and implementation identity.
- Complete agent-owned or terminal authentication before starting a session.
- Create a harmless session and verify working-directory binding.
- Verify streaming messages, tool calls, file diffs, terminal rendering, permission requests, cancellation, and any advertised load, resume, fork, list, close, mode, or config-option behavior independently.
- Verify forwarded MCP servers separately from the agent's native MCP config.
Completed v1 additions include generic session configuration options,
session/list, session-information updates, session/resume, and
session/close. Elicitation, boolean config-option refinements,
session/delete, logout, additional directories, remote transports, and the v2
prompt lifecycle remain draft RFDs unless the live ACP documentation says they
have advanced. Gate experimental behavior on explicit capabilities and label
it as draft in reports.
What ships with it
3 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 · 85 lines · 47 tokens per session scan A 3a5a1e5465fe
operate-acp-agent-integration is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 847 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…