machinemode.io
Registry · updated 2026-07-30

Tools

Tools that implement, adapt or measure the Machine Mode standard.

Entries are self‑declared, not certified, and each one links to a public repo where you can inspect the implementation, check the badge claim and rerun conformance yourself. A scaffold is a repo with no working implementation, and it's listed as one.

Conforming
1
Scaffold
4
Adapter / wrapper
1

Conforming

conforming · 1 entryPasses the § 18 checklist for the factors it claims.

  1. aoi-probe

    linter · javascript
    aoi-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.

    repo →MITby Kevin Hunt

Scaffolds

in-development · 4 entriesThe repo exists; there’s no working implementation yet.

  1. aoi-cli-sdk-ts

    SDK · typescript
    aoi-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.

    repo →MITby Kevin Hunt

  2. aoi-coreutils

    tool · javascript
    aoi-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.

    repo →MITby Kevin Hunt

  3. aoi-lint

    linter · typescript
    aoi-cli v1.0-alpha

    The conformance checker for AOI-CLI tools.

    Will run the §18 conformance checklist against any CLI invocation: JSONL output, schema discovery, completion semantics, signal handling and redaction, emitting AOI events itself while it works. In development; not yet usable.

    repo →MITby Kevin Hunt

  4. machinemode

    wrapper · typescript
    aoi-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.

    repo →MITby Kevin Hunt

Adapters and wrappers

adapter · 1 entryWraps a non‑AOI upstream tool to give it an AOI interface.

  1. aoi-jc

    wrapper · python
    aoi-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.

    repo →MITby Kevin Hunt

List your tool

The registry is one JSON file, content/tools.json. Open a PR that adds your entry with the name, repo, language, AOI profile and version, a one‑line tagline and a longer description. Merged entries go live with the next deploy.

content/tools.jsonjson
{
  "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" }]
}

Status values: conforming means the tool passes the § 18 checklist; in-developmentmeans it's working toward that but doesn't conform yet; adapter means it wraps a non‑AOI upstream tool to give it an AOI interface.

View the registry source →Get a conformance badge

No central authority verifies these claims. That's aoi-lint's job, and because the repos are public, anyone can check for themselves. The conformance checklist is § 18 of the AOI‑CLI spec.