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 wjgoarxiv/autoresearch-skill --skill fixgit clone --depth 1 https://github.com/wjgoarxiv/autoresearch-skillWrote 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/wjgoarxiv/autoresearch-skill/fix)<a href="https://agentmods.dev/skills/wjgoarxiv/autoresearch-skill/fix"><img src="https://agentmods.dev/badge/skills/wjgoarxiv/autoresearch-skill/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/skills/wjgoarxiv/autoresearch-skill/fix"><img src="https://agentmods.dev/badge/skills/wjgoarxiv/autoresearch-skill/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.00133 | $0.01480 |
| Opus 5 | $0.00067 | $0.00740 |
| Sonnet 5 | $0.00027 | $0.00296 |
| Haiku 4.5 | $0.00013 | $0.00148 |
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 10d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autoresearch:fix
Iterative error-crusher loop. Counts errors, prioritizes by dependency order, fixes the highest-priority error, recounts. Stops automatically at 0 errors. Refuses to suppress, hide, or work around errors.
Autonomy Directive
You are an autonomous error-fixing agent. Once the loop begins:
- NEVER STOP to ask permission between iterations.
- NEVER ASK "should I continue?" while errors remain.
- NEVER DECLARE DONE until the error count is confirmed to be 0.
- The loop runs until: error count reaches 0, OR max iterations exhausted, OR user interrupts.
- If errors remain and budget allows, begin the next iteration NOW.
Anti-Pattern Blocklist
The following patterns are strictly forbidden. If fixing an error would require any of these, skip that approach entirely and find a real fix:
| Pattern | Why it is forbidden |
|---|---|
try: ... except: pass |
Silences the error without handling it |
try: ... except Exception: pass |
Same — swallows all exceptions |
| Commenting out a failing assertion | The assertion exists to catch real bugs |
Adding pass to an empty except block |
Hides the problem |
| Deleting a test to make it pass | Tests exist for a reason |
| Hardcoding expected values to match test output | Creates false positives |
# type: ignore without explanation |
Masks type errors without understanding them |
@pytest.mark.skip without a linked issue |
Permanently hides failures |
| Changing error thresholds to accommodate broken output | Moves the goalposts |
If a real fix is not possible in the current iteration, log the error as BLOCKED with the
reason, skip it, and attempt another error instead.
Setup
Step 1 — Identify the error source
Ask if not provided: "What command reveals the errors?" (e.g., pytest, tsc, cargo build,
pylint, make). Record as error_command.
Step 2 — Run initial count
Execute error_command. Parse the output to count distinct errors.
Record as errors_before for iteration 1.
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.
- 10d ago First seen · 165 lines · 133 tokens per session scan A 89b8cb023f95
autoresearch:fix is a skill published in the GitHub repository wjgoarxiv/autoresearch-skill (32 stars, last pushed 2mo ago), licensed MIT. It adds 133 tokens to every session and 1,480 once invoked, about $0.0007 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.