The pack · open machinery · MIT

/api — the Stream Engineer

A staged build of your passive stream, run by an agent team in your own terminal and repo. Not a course you watch — machinery that ranks the archetypes against your real inventory, wires your surfaces, scaffolds the engine, and holds you to your own kill criteria.

The pack · /api · open machinery

Not another course about streams. The stream itself, as code.

/api is a stream engineer in your terminal: five staged commands, four specialist agents, four skills — installable in Claude Code, portable to Codex, Gemini CLI, Cursor, and OpenCode. Every stage ends with a written artifact in yourrepo. Advice that lives only in a chat doesn't exist.

/plugin marketplace add frankxai/agenticpassiveincome

/plugin install api-pack@agenticpassiveincome

Pack details Read the source — it's MIT

claude — /api session

/api streams

Reading inventory… newsletter (2.3k) · site (evergreen, 41 pages) · 12 honest hrs/mo

Struck 9 of 12 archetypes by arithmetic — labor floor or latency over budget.

Ranked fit: 04 newsletter+recs · 01 affiliate publication · 03 product line

Kill criterion locked: first revenue event by Oct 15 — or sunset.

→ wrote streams/00-stream-selection.md

/api connect

Mapping surfaces… newsletter carries · site converts · X feeds.

Nothing gets built that an owned surface already does.

→ wrote streams/01-surface-map.md

/api engine

The five stages

Every stage ends in a written artifact.

/api streamsRanks the 12 stream archetypes against your surfaces, skills, and honest hours — eliminations cited from the atlas, kill criterion mandatory before anything is written.streams/00-stream-selection.md

/api connectMaps your existing website, socials, and newsletter into the stream plan — what feeds, what carries, what gets built new. Nothing gets built that an owned surface already does.streams/01-surface-map.md

/api engineScaffolds the machine: registry, templates, integrity gates, pipeline config. Registry first, always — automating generation before the gates exist just industrializes error.streams/02-engine-spec.md

/api loopInstalls the recurring automation — idempotent, capped, observable, gated. No loop earns direct publish rights, ever.streams/03-loops.md

/api auditFreshness and integrity pass on a running stream: stale facts, dead links, disclosure presence, program-term drift.streams/audits/YYYY-MM.md

Doctrine, non-negotiable: no income promises — labor floors published on every stream. One stream at a time. Every stream gets a kill criterion at selection. Honest costs on everything. Disclosure by default. If it lives only in a chat, it doesn't exist.

The team inside

Four specialists, one quality floor.

stream-engineer

Lead — ranks the 12 archetypes against your real inventory, designs the chosen machine, owns the honest economics and the kill criterion.

content-machine

Pipeline builder — scaffolds registries, templates, and gates; generates artifacts with evidence labels from registry facts. Never publishes.

seo-editor

Search + GEO — optimizes for organic search and LLM citation while keeping every claim sourced and dated. Owns freshness discipline.

syndicator

Distribution loops — cuts canonical long-form into platform-native derivatives that link back home. One canonical, many cuts.

Runtimes

Claude Code first. Portable everywhere.

The richest experience is the Claude Code plugin — one-command install, subagent fan-out, scheduled loops. The pack's intelligence is plain markdown, so Codex, Gemini CLI, Cursor, and OpenCode run the full system via the portable guide. Runtimes churn quarterly; your stream architecture shouldn't.

Get the pack on GitHub Pick your stream first