autoresearch is an agent workflow that repeatedly changes a project, verifies a measurable result, keeps or discards the change, and continues iterating toward a goal. It is for autonomous improvement tasks in Claude Code, OpenCode, and OpenAI Codex across domains with mechanical success measures. The catalogue contains its commands, hooks, skills, plugin, agent, and instruction.
Borrowing it
Nothing to install: this file belongs to uditgoenka/autoresearch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/uditgoenka/autoresearch/master/.claude/commands/autoresearch/fix.mdgit clone --depth 1 https://github.com/uditgoenka/autoresearchWrote 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/commands/uditgoenka/autoresearch/fix)<a href="https://agentmods.dev/commands/uditgoenka/autoresearch/fix"><img src="https://agentmods.dev/badge/commands/uditgoenka/autoresearch/fix/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/commands/uditgoenka/autoresearch/fix"><img src="https://agentmods.dev/badge/commands/uditgoenka/autoresearch/fix.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.00022 | $0.01147 |
| Opus 5.5 | $0.00009 | $0.00459 |
| Sonnet 5.5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
autoresearch:fix 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- autoresearch_fix — 97% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EXECUTE IMMEDIATELY.
Parse Arguments
Extract from $ARGUMENTS:
Target:or--target— command that shows errors (e.g.,npm test,tsc --noEmit)Scope:or--scope— file globs to modifyGuard:or--guard— safety command (must always pass)Iterations:or--iterations— default 20. "unlimited" for unbounded.--from-debug— read handoff.json from previous debug run--category— filter: test, type, lint, build--evals,--evals-interval N,--chain
Setup (if required context missing)
If Target and Scope both missing:
- Auto-detect failures: run test suite, type checker, linter, build
- Present results via AskUserQuestion (single batched call): Q1 (Fix What): "Found [N] test failures, [M] type errors, [K] lint errors. Fix what?" — everything, only tests, only types, only lint Q2 (Guard): "Safety command that must always pass?" — npm test, tsc, npm run build, skip Q3 (Scope): "Which files can I modify?" — suggested globs from error locations + all Q4 (Launch): "Ready?" — fix until zero, fix with limit, cancel If all provided → skip setup. If --from-debug → read handoff.json for scope and findings.
Precondition Checks
Verify: git repo exists, clean working tree, no lock files, no detached HEAD. Fail fast on critical issues.
Establish Baseline (Iteration 0)
- Run Target command → count errors (metric = error count, direction = lower_is_better)
- Record baseline in TSV
- Create output directory:
autoresearch/fix-{YYMMDD}-{HHMM}/ - TSV header:
# metric_direction: lower_is_better\niteration\ttimestamp\terror_type\terror_fixed\tcommit\tmetric\tdelta\tguard\tstatus\tdescription
Iteration Loop (until zero errors or max_iterations)
Phase 1: Review
- Read results TSV + git log
- Run Target to get current error list
- If error count == 0 → exit loop (SUCCESS)
Phase 2: Prioritize
Order: crash/fatal → test failures → type errors → lint → warnings. Within category: easiest first (single-file fixes before cross-file).
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 · 103 lines · 22 tokens per session scan A 664467ca4bba
autoresearch:fix is a command published in the GitHub repository uditgoenka/autoresearch (6,763 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,147 once invoked, about $0.0001 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-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
fix
Universal debugging and fix application with semantic code analysis.