Stack
One pick per harness component, and the accounts an agent acts through
Picks as of . Re-derive their evidence from the repository withnode scripts/stack-evidence.mjs
Inside the harness
Needs the armory CLI · not on npm yet, build it from cli/ in the repository
One command for these picks
armory install karpathy-coding-discipline --cli claude && \armory install github-mcp --cli claudeNot in the command, set them up from the source: letta-ai-letta, superpowers, playwright-cli, plannotator, wshobson-agents, pocketflow, promptfoo, langfuse, e2b-sandbox
https://armory-murex.vercel.app/stackAccounts the agent acts through
These are accounts, not repositories, so they carry no Armory score; each line says how an agent gets access.
| Slot | Pick | Deploy access |
|---|---|---|
| Computer | Orgo | ORGO_API_KEY, provisioned through bezalel.sh so the agent never sees the key |
| Sandbox | E2B | E2B_API_KEY, one microVM per run |
| Database | Supabase | URL and anon key to the agent; the service-role key is injected at the tool boundary, never into a prompt or a log |
| AgentMail | API key and a per-inbox webhook secret (starts whsec_); verify the signature, or the route is an open relay | |
| Phone / SMS / WhatsApp | Twilio | account SID, auth token and a purchased number; inbound requests are signed with X-Twilio-Signature |
| iMessage | Photon Spectrum | project id and secret, and the owner pairs their own handle with a one-time code (OTP) |
| Card / spend | Agent Card HQ | an identity check (KYC), then a funded balance; the slowest slot, so start it first |
| Payments / earn | Stripe agent-toolkit | a restricted key scoped to the agent, never the account key |
| Memory store | Supermemory | SUPERMEMORY_API_KEY, or self-host |
| Connectors | Composio | a key, plus the owner's OAuth consent per app; the agent never holds the third-party token |
| Deploy / hosting | Vercel | token and a linked project; after a CLI deploy, vercel alias set is a separate step, or nothing ships |
| Web / browser | Browserbase + Stagehand | key and project id, or local Chromium on the owner's profile, read-only |
Start the slow slots first: the card needs an identity check (KYC) and iMessage needs the owner's one-time code, and both take days; then buy the phone number, then set up the email inbox and its webhook secret; everything that only needs a key takes a minute.
API returns both lists as JSON; Components lists up to three picks per component with its top-ranked rows.