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 echoomegaprime/echo-qcoder --skill qcoder-session-operatorgit clone --depth 1 https://github.com/echoomegaprime/echo-qcoderWrote 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/echoomegaprime/echo-qcoder/qcoder-session-operator)<a href="https://agentmods.dev/skills/echoomegaprime/echo-qcoder/qcoder-session-operator"><img src="https://agentmods.dev/badge/skills/echoomegaprime/echo-qcoder/qcoder-session-operator/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/echoomegaprime/echo-qcoder/qcoder-session-operator"><img src="https://agentmods.dev/badge/skills/echoomegaprime/echo-qcoder/qcoder-session-operator.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.00092 | $0.00719 |
| Opus 5.5 | $0.00037 | $0.00288 |
| Sonnet 5.5 | $0.00018 | $0.00144 |
| Haiku 4.5 | $0.00009 | $0.00072 |
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 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 — 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, thenget_qcoder_sessionwhen detail is needed. - For new work, call
preview_qcoder_taskfirst. Stop if it rejects the workspace, role, or policy. - Summarize the accepted preview and call
start_qcoder_sessionwith the returned fingerprint and a new idempotency key. - Use
send_qcoder_taskonly for a returned session ID and its latest revision. Refresh onCONFLICTbefore deciding whether to retry. - Call
render_qcoder_consoleonly 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_sessionwith 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
builderfor ordinary implementation,cli-buildfor 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.
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 · 47 lines · 92 tokens per session scan A a09c18e4b0f0
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.0004 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.