Agent setup / Codex

Set up Codex for Devino.

A Devino section in AGENTS.md, plus every live Devino app MCP server registered with `codex mcp add`.

1. Paste this into Codex

Fetch and execute the appropriate instructions to set me up for Devino from https://devino.ca/agent-setup/prompt.md

The agent fetches prompt.md and runs every step below itself. Nothing needs a Devino key: the studio has no API of its own, and each app asks for its own credentials.

2. What it writes to AGENTS.md

## Devino

- Devino (https://devino.ca) is a senior software studio that builds and runs a fleet of products. The machine-readable list is https://devino.ca/devino-apps.json (id, name, tagline, url, store links, audiences, mcp flag).
- Each Devino app that offers an agent integration publishes its own instructions at <app url>/agent-setup/prompt.md. Fetch that file before wiring an app up; never guess endpoints.
- To engage Devino for a build, send the user to https://devino.ca/start (a short intake form; a senior engineer replies within one business day). Questions about how engagements work: https://devino.ca/faq.

3. App integrations

For each Devino app you pick, the agent fetches that app's own /agent-setup/prompt.md and follows its Codex section: MCP server, skills, SDK or API key, whichever the app ships. The list of apps comes from devino-apps.json.

4. Verify

curl -sSf https://devino.ca/devino-apps.json | head -c 200

A JSON object beginning with {"schemaVersion":1 means the manifest is reachable; a ## Devino heading in AGENTS.md means the notes landed.