Tools.
A registry of tools that implement, or aim to implement, the Machine Mode standard.
Self-declared, not certified. Each entry links to a public repo where the implementation can be inspected, the badge claim verified, and conformance retested. To add yours, submit a PR against content/tools.json.
- aoi-cli-sdk-tsSDK · typescriptaoi-cli v0.2
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 · typescriptaoi-cli v0.2
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 v0.2
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 v0.2
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.
- machinemode-claudeskill · markdownaoi-cli v0.2
Claude Code skill for authoring AOI-CLI tools.
Walks a developer through making their CLI AOI-conformant. Generates the boilerplate from the /adopt guide, runs aoi-lint after each iteration, suggests fixes.
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": "0.2" }],
"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).