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/recca0120/code-quest/socket-ionpx skills add recca0120/code-quest --skill socket-iogit clone --depth 1 https://github.com/recca0120/code-questWhat 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.00035 | $0.01975 |
| Opus 5 | $0.00017 | $0.00988 |
| Sonnet 5 | $0.00007 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
socket-io 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 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.
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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Socket.IO Conventions
Event Naming: type:subtype
| Prefix | Direction | Examples |
|---|---|---|
session: |
C→S / S→C | session:launch, session:init, session:created |
chat: |
C→S | chat:send, chat:cancel, chat:respond |
message: |
S→C | message:assistant, message:user, message:result |
stream: |
S→C | stream:chunk, stream:end, stream:block_start |
control: |
S→C | control:permission, control:elicitation |
system: |
S→C | system:task_started, system:hook_started |
notification: |
S→C | notification:toast, notification:auth_status |
file: |
C→S | file:read, file:list |
git: |
C→S | git:log, git:diff, git:checkout, git:status, git:exec |
app: |
C→S | app:init, app:get_provider_config |
auth: |
C→S | auth:login, auth:submit_oauth_code, auth:get_status |
settings: |
C→S | settings:set_model, settings:apply, settings:get_state |
mcp: |
C→S | mcp:get_servers, mcp:reconnect, mcp:authenticate |
plugin: |
C→S | plugin:install, plugin:list, plugin:list_marketplaces |
plan: |
C→S | plan:comment, plan:get_comments, plan:close_preview |
speech: |
C→S | speech:start, speech:stop |
terminal: |
C→S | terminal:get_contents, terminal:open_claude |
All C→S events use namespace:action format. No bare event names.
Session Event Payload Reference
session:launch (C→S, callback)
Client sends: socket.emit('session:launch', { channelId, cwd, ...opts }, callback)
Server handler: apps/server/src/socket/handlers/session/connect.ts → handleLaunch()
Server flow:
channelManager.create(channelId, { launchOptions, initOptions, cwd })- Sends
session:initializeto runner (CLI) - On
session:initfrom runner → broadcastssession:created+session:states - Persists session to DB via
sessionStore.persist() - Callback responds
Success: { channelId, slashCommands?, models?, account? }
Error: { error: string }
Schema: sessionLaunchResponseSchema
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 · 206 lines · 35 tokens per session scan A c78cc79bd90b
socket-io is a skill published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,975 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…