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/.opencode/commands/autoresearch_ship.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/autoresearch_ship)<a href="https://agentmods.dev/commands/uditgoenka/autoresearch/autoresearch_ship"><img src="https://agentmods.dev/badge/commands/uditgoenka/autoresearch/autoresearch_ship/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/autoresearch_ship"><img src="https://agentmods.dev/badge/commands/uditgoenka/autoresearch/autoresearch_ship.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.00019 | $0.00978 |
| Opus 5 | $0.00010 | $0.00489 |
| Sonnet 5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
autoresearch_ship 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 11d 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.
This is a copy
98% identical to autoresearch:ship — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 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— what to ship (path, PR, artifact, deployment)--type <type>— override auto-detection: code-pr, code-release, deployment, content, docs, package, config--dry-run— validate everything but don't ship--auto— auto-approve if no errors found--force— skip non-critical items (blockers still enforced)--rollback— undo last ship action--monitor N— post-ship monitoring for N minutes--checklist-only— only generate checklist, don't execute--chain,--<subcommand>
Remaining text = description of what to ship.
Setup (if Target or Type unclear)
- Auto-detect ship type from context:
- Has uncommitted changes or PR → code-pr
- Has version bump / changelog → code-release
- Has Dockerfile / deploy config → deployment
- Has markdown / content files → content
- Has package.json version change → package
- If still unclear → question (single batch): Q1 (What): "What are you shipping?" — code PR, release, deployment, content, docs, package Q2 (Target): "Specific target?" — current branch, specific PR, specific path Q3 (Mode): "How to ship?" — full workflow, dry-run only, checklist only If all clear → skip.
Phase 1: Identify
- Determine ship type (auto-detected or --type override)
- Identify target artifact(s)
- Map to domain-specific checklist
Phase 2: Inventory
Gather everything that will be shipped:
- Files changed (git diff)
- Dependencies affected
- Config changes
- Migration files
- Breaking changes
Phase 3: Checklist
Generate domain-specific checklist:
Code PR: tests pass, types check, lint clean, no secrets, PR description, reviewers assigned Release: version bumped, changelog updated, migration tested, rollback plan Deployment: env vars set, health checks configured, rollback ready, monitoring active Content: links valid, images optimized, SEO metadata, spell check Package: version bumped, README updated, breaking changes documented, CI green
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.
- 11d ago First seen · 121 lines · 19 tokens per session scan A 24f70f5581e4
autoresearch_ship is a command published in the GitHub repository uditgoenka/autoresearch (6,270 stars, last pushed 29d ago), licensed MIT. It adds 19 tokens to every session and 978 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to autoresearch:ship, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
doc-changelog
Generation and maintenance of the project changelog.