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/echoomegaprime/echo-qcoder/qcoder-autonomous-issue-solvernpx skills add echoomegaprime/echo-qcoder --skill qcoder-autonomous-issue-solvergit clone --depth 1 https://github.com/echoomegaprime/echo-qcoderWhat 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.00075 | $0.00496 |
| Opus 5 | $0.00037 | $0.00248 |
| Sonnet 5 | $0.00015 | $0.00099 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
qcoder-autonomous-issue-solver 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.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QCoder Autonomous Issue Solver
Expected input
Require a concrete outcome, a scoped repository, and an executable or observable acceptance condition. Derive missing technical detail from code, tests, logs, and live state before asking.
Autonomous loop
- Read instructions and record the starting branch, revision, dirty files, and acceptance command.
- Reproduce the failure or create a failing test. If reproduction is impossible, collect direct evidence and state the falsifiable hypothesis.
- Build a minimal repository map with semantic navigation, manifests, entry points, tests, and recent history.
- Make exactly one evidence-backed change at a time. Before each change, record hypothesis, supporting evidence, falsifier, rollback, and expected result.
- Run the narrowest useful check. On failure, diagnose the mechanism before editing again; retain useful evidence and abandon disproven hypotheses.
- Escalate through focused, related, full, and security verification. Use the todo stop guard to continue unfinished work, but never loop past eight repair attempts without a new hypothesis or new evidence.
- Inspect the final diff, prove unrelated changes remain untouched, commit only owned files when required, register the result, and checkpoint durable evidence.
The installed mini-SWE-agent CLI is a reference and benchmark tool, not delegated authority. Do not start a second autonomous agent unless the mission explicitly calls for it. Aider, Goose, and OpenHands contribute workflow patterns only until separately benchmarked and promoted.
Facts that must not be inferred
Never infer test success, issue closure, commit or push state, deployment, target ownership, or rollback readiness. Read the source of truth.
Stop conditions
Stop at a doctrine hard limit, missing authorization, irreducible ambiguity that would change product behavior, exhausted evidence paths, or a failing rollback test. Preserve the working tree and report the exact blocker.
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 · 35 lines · 75 tokens per session scan A 8271c3465e95
qcoder-autonomous-issue-solver is a skill published in the GitHub repository echoomegaprime/echo-qcoder (0 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 496 once invoked, about $0.0004 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.