Tools.
A registry of tools that implement, or aim to implement, the Machine Mode standard.
Self-declared, not certified. Each entry links to a repo that resolves where the implementation can be inspected, the badge claim verified, and conformance retested. To add yours, submit a PR against content/tools.json.
- aoi-probelinter · javascriptaoi-cli v1.0-alpha
Measures what any CLI's machine-output mode actually does.
Assumption-free measurement instrument. Runs an arbitrary command and answers a graded questionnaire: per-line JSON validity, discriminator field name, output-format version declaration, terminal completion event, explicit success boolean, stderr cleanliness, pipe-close behaviour. Makes no AOI assumptions, so it can measure non-conforming tools — which is the point. Emits AOI events itself. Backed by a 22-assertion ground-truth suite.
- aoi-cli-sdk-tsSDK · typescriptaoi-cli v1.0-alpha
TypeScript SDK for building AOI-CLI tools.
Event emitter, schema helpers, pipe-safe stdout, redaction utilities, terminal-summary contracts. The boilerplate from the /adopt guide, factored into a library.
- aoi-coreutilstool · javascriptaoi-cli v1.0-alpha
Native AOI re-implementations of the most-used Unix utilities.
First-class AOI tools written from scratch — aoi-ls, aoi-find, aoi-grep, aoi-cat, aoi-wc, aoi-head, aoi-tail, aoi-sort, aoi-uniq, aoi-du, aoi-stat, aoi-cp, aoi-mv, aoi-rm. Identical output shape across operating systems (no GNU vs BSD quirks). Clean event emission, no text parsing. Sibling to machinemode: machinemode covers any system tool by wrapping it; aoi-coreutils gives the most-critical tools a reliable, OS-independent native implementation.
- aoi-lintlinter · typescriptaoi-cli v1.0-alpha
The conformance checker for AOI-CLI tools.
Runs the §18 conformance checklist against any CLI invocation. Validates JSONL output, schema discovery, completion semantics, signal handling, and redaction — and itself emits AOI events while it works.
- machinemodewrapper · typescriptaoi-cli v1.0-alpha
An AOI mode for ls, find, grep, and the other coreutils-class tools agents touch constantly.
machinemode <tool> ...args wraps an existing non-AOI tool (ls, find, grep, cat, wc, du, stat, cp, mv, sort, uniq, awk, sed, xargs, rg, jq, curl, git log, ...) and emits its output as a typed AOI event stream. Per-tool adapter modules; one PR per upstream tool. Works against the system's existing binaries — nothing new to install on the target side. The pragmatic, broad-coverage answer to the coreutils gap.
- aoi-jcwrapper · pythonaoi-cli v1.0-alpha
Wraps jc's 236 parsers in an AOI envelope.
jc normalises the output of ~236 Unix tools into JSON but has no envelope, no completion event, no error taxonomy, and no exit-status contract. This adapter supplies exactly that layer: aoi:meta with jc provenance, per-record entry events, jc's per-line _jc_meta failures mapped to typed aoi:error, and a synthesised terminal aoi:summary with a real exit code. Verified end-to-end. Note the limit: a jc standard parser fed the wrong input returns plausible JSON at exit 0, and no envelope can detect that.
List your tool.
The registry is a single JSON file. Open a PR adding your tool's entry — name, repo, language, AOI profile + version, a short tagline, a longer description. Submissions land in the next deploy.
{
"name": "your-tool",
"tagline": "One sentence on what it does.",
"description": "A paragraph on what it does, who it's for, what it covers.",
"status": "in-development",
"kind": "tool",
"repo": "https://github.com/you/your-tool",
"homepage": null,
"profiles": [{ "name": "aoi-cli", "version": "1.0-alpha" }],
"language": "typescript",
"license": "MIT",
"maintainers": [{ "name": "Your Name", "url": "https://github.com/you" }]
}Allowed status values: conforming (passes the §18 checklist), in-development (not yet conforming but actively working toward it), or adapter (wraps a non-AOI upstream tool to present an AOI interface).