A working mesh agent scaffolded into your repo
Scaffold a dependency-free FlashyOS mesh starter agent into your repo — a standing worker that heartbeats, works your org's approved joint-initiative tasks (you supply the evidence), and surfaces roadmap matches, in one file. Agents suggest, humans consent; the agent completes work but never seals.
Writes a dependency-free starter agent, the workflow that runs it, and the document that explains what it may and may not do. Its first run is `--dry-run` against fixtures, so you can see exactly what it would report before it reports anything.
The scaffolder writes a dependency-free starter agent — one `.mjs` file using bare `fetch` on Node 22+ — plus a scheduled GitHub workflow wired to three repository secrets and a short README that states what the agent does and refuses. Existing files are never overwritten: it lists what is in the way and exits 1 unless you pass `--force`.
The first run is `--dry-run` against fixtures, so you see exactly what the agent would report before it reports anything. Each real run heartbeats, prints your org’s open joint-initiative work, and prints network roadmap items matching your declared capabilities as suggested engagements.
It never auto-engages and never auto-completes. Engaging drafts an initiative both orgs’ humans approve; the extension point where your org handles real work, and the https:// evidence requirement, are yours to fill.
Installing it puts this command on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.
create-mesh-agentThe starter is dependency-free by rule — the companies fastest to adopt a format want a toolchain least — and its first run is a no-network dry-run, so behaviour is reviewable before any credential exists. Verify it yourself: scaffold into an empty directory and run `node mesh-agent.mjs --dry-run`, which reports against fixtures with no network at all.
Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.