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/patrickjaiin/claude-code-connect/connectnpx skills add PatrickJaiin/claude-code-connect --skill connectgit clone --depth 1 https://github.com/PatrickJaiin/claude-code-connectWhat 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.00048 | $0.00638 |
| Opus 5 | $0.00024 | $0.00319 |
| Sonnet 5 | $0.00010 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade C, and why
connect scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If the user wants to stop the child's listen mode: `touch ~/.claude/claude-connect/sessions/<name>/stop`. To merely detach while leaving the child listening, just stop sending prompts. To clean up a dead session's files: How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect — attach to a listening child session
Drive another Claude Code session that ran /listen. Communication is via files under ~/.claude/claude-connect/sessions/<name>/. All scripts referenced below live in this skill's scripts/ directory.
Finding and attaching
/connectwith no arguments → runbash <skill-dir>/scripts/list.sh, show the user each session's name, status (LISTENING / WORKING / STALE), working directory, and summary preview, then ask which to attach to. If exactly one is LISTENING, suggest it./connect <name>(or after the user picks) → read~/.claude/claude-connect/sessions/<name>/summary.mdandmeta.json, present the child's summary to the user, and remember<name>as the connected session for the rest of this conversation. Warn (but still attach) if the session looks STALE./connect <name> <prompt...>→ attach as above, then immediately send the rest of the arguments as the first prompt.
Sending a prompt and reading the reply
When the user asks you to send something to the child (e.g. "ask it to run the tests", "tell it to refactor X"):
- Write the prompt to a temp file (use the scratchpad dir), phrased as a clear standalone instruction — the child has its own context but none of this conversation's.
NNN=$(bash <skill-dir>/scripts/send.sh <name> <prompt-file>)— prints the sequence number.bash <skill-dir>/scripts/await.sh <name> $NNNwith the Bash timeout parameter set to 600000. It prints one of:=== REPLY NNN ===+ body → show the child's reply to the user (quote it substantially, don't over-compress; make clear it's the child speaking).=== TIMEOUT (state: working) ===→ the child is still working; runawait.shagain. Keep re-running while state isworkingunless the user interrupts.=== CHILD NOT LISTENING ===→ the child session's heartbeat went stale (its user may have interrupted it or closed the session). Tell the user; the prompt file stays queued and the child will pick it up if/listenis resumed there.
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.
- 2d ago First seen · 32 lines · 48 tokens per session scan C eecca2b8e475
connect is a skill published in the GitHub repository PatrickJaiin/claude-code-connect (2 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 638 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…