What is qcoder-session-operator?

A session controller for QCoder, a local coding assistant that builds software. It lets an authorized user preview work, start and monitor a workspace session, send limited follow-up tasks, view its console, or stop it.

Use it to start QCoder coding jobs, check their status or history, send bounded instructions, display session output, and cancel running work.

It provides a controlled way to manage QCoder work without guessing which workspace or session is involved. It also checks whether requested work is allowed before starting it.

qcoder-session-operator — Skill by echoomegaprime

Install

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.

agentmods

npx agentmods add skills/echoomegaprime/echo-qcoder/qcoder-session-operator

Any agent

npx skills add echoomegaprime/echo-qcoder --skill qcoder-session-operator

Clone the repo

git clone --depth 1 https://github.com/echoomegaprime/echo-qcoder

Made for: Claude Code, Codex.

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 719 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00092	$0.00719
Opus 5	$0.00046	$0.00360
Sonnet 5	$0.00018	$0.00144
Haiku 4.5	$0.00009	$0.00072

Measured yesterday against content hash a09c18e4b0f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

qcoder-session-operator 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.

skills/qcoder-session-operator/SKILL.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QCoder Session Operator

Use the QCoder MCP tools as a goal-oriented session controller. Never approximate the workflow with a shell command or infer a workspace path, session ID, authorization, completion state, or test result.

Expected input

Identify the user's intended outcome, registered workspace key, fleet role, mission, and task. A direct request to operate QCoder is required. If the user refers to "that session," resolve it with list_qcoder_sessions; ask only when multiple plausible owned sessions remain.

Required sequence

For status or history, call list_qcoder_sessions, then get_qcoder_session when detail is needed.
For new work, call preview_qcoder_task first. Stop if it rejects the workspace, role, or policy.
Summarize the accepted preview and call start_qcoder_session with the returned fingerprint and a new idempotency key.
Use send_qcoder_task only for a returned session ID and its latest revision. Refresh on CONFLICT before deciding whether to retry.
Call render_qcoder_console only after current session data has been retrieved and the user benefits from the visual console.
For cancellation, refresh the session, state the exact target and effect, then call stop_qcoder_session with the latest revision and exact confirmation literal. Do not stop other processes.
Report only the state and evidence returned by the tools. A queued or running task is not complete.

Decision points

Use builder for ordinary implementation, cli-build for launcher/CLI work, and another fleet role only when its responsibility materially matches the task.
When QCoder is busy, accept the returned queue position; do not start a parallel process outside the controller.
If authentication is missing or scopes changed, surface the tool's relink challenge. Never request or handle a token.
If a mutation's transport result is uncertain, retry the exact request with the same idempotency key.
If the user changes the task payload, use a new idempotency key.

Read the full file on GitHub · 47 lines

Files

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.

Changes

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 · 47 lines · 92 tokens per session scan A a09c18e4b0f0

Subscribe to this mod's changes

qcoder-session-operator is a skill published in the GitHub repository echoomegaprime/echo-qcoder (0 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 719 once invoked, about $0.0005 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-31.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens