How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

impl:model - Prompt - OpenSmartRoute

Name: impl:model
Author: helalifaker

Prompt file imported from helalifaker/budfin (.codex/prompts/impl.model.md). Copyright stays with the author.

Internal command. Called by /impl:story automatically.

Internal scaffolding command. Called by story-orchestrator agents during /impl:story. Not intended for direct user invocation.

Parse the argument:

ModelName: PascalCase model name (e.g., "Enrollment", "StaffMember", "FiscalYear")

If missing, ask the user: "What is the name of the Prisma model you want to scaffold?"

Step 1 — Invoke Skill

Use the Skill tool to invoke: prisma-model

This skill handles all model scaffolding with correct BudFin patterns (Uint8Array for binary fields, DECIMAL(15,4) for monetary fields, P2025 error handling). Follow the skill exactly.

Step 2 — Verify Schema Updated

After the skill writes to apps/api/prisma/schema.prisma:

Read the schema file and confirm the new model block exists
Verify field types follow BudFin conventions:
- Monetary fields: Decimal (maps to DECIMAL(15,4))
- Encrypted salary fields: Bytes (maps to Uint8Array in TypeScript — Prisma 6)
- IDs: String @id @default(uuid())
- Timestamps: DateTime @default(now()) / DateTime @updatedAt

Step 3 — Generate and Migrate

pnpm --filter @budfin/api exec prisma generate

Confirm generation succeeds (zero errors).

pnpm --filter @budfin/api exec prisma migrate dev --name add-$MODEL_SLUG

Where $MODEL_SLUG is the lowercase kebab-case of the model name. Example: "StaffMember" → add-staff-member

Confirm the migration runs cleanly.

If migration fails:

Show the error
Check for conflicting model names, duplicate fields, or missing relations
Fix and re-run

Step 4 — Output

Model scaffolded: $ModelName

Schema: apps/api/prisma/schema.prisma
Migration: apps/api/prisma/migrations/[timestamp]_add-$MODEL_SLUG/

Prisma client generated — TypeScript types are now available.

Remember:
  - Binary (encrypted) salary fields are Uint8Array in TypeScript, NOT Buffer (Prisma 6)
  - Use P2025 error code when record not found (NotFoundError was removed in Prisma 6)
  - Monetary fields come back as Decimal type — wrap in new Decimal(value) for arithmetic

Next: Add service layer and route, or run /impl:route "[resource]" "[method]"

Install impl:model and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

> **Internal command.** Called by `/impl:story` automatically. > **Internal scaffolding command.** Called by story-orchestrator agents during /impl:story. > Not intended for direct user invocation. Parse the argument: - `ModelName`: PascalCase model name (e.g., "Enrollment", "StaffMember", "FiscalYear") If missing, ask the user: "What is the name of the Prisma model you want to scaffold?" ## Step 1 — Invoke Skill Use the Skill tool to invoke: `prisma-model` This skill handles all model scaffolding with correct BudFin patterns (Uint8Array for binary fields, DECIMAL(15,4) for monetary fields, P2025 error handling). Follow the skill exactly. ## Step 2 — Verify Schema Updated After the skill writes to `apps/api/prisma/schema.prisma`: 1. Read the schema file and confirm the new model block exists 2. Verify field types follow BudFin conventions: - Monetary fields: `Decimal` (maps to `DECIMAL(15,4)`) - Encrypted salary fields: `Bytes` (maps to `Uint8Array` in TypeScript — Prisma 6) - IDs: `String @id @default(uuid())` - Timestamps: `DateTime @default(now())` / `DateTime @updatedAt` ## Step 3 — Generate and Migrate ```bash pnpm --filter @budfin/api exec prisma generate ``` Confirm generation succeeds (zero errors). ```bash pnpm --filter @budfin/api exec prisma migrate dev --name add-$MODEL_SLUG ``` Where `$MODEL_SLUG` is the lowercase kebab-case of the model name. Example: "StaffMember" → `add-staff-member` Confirm the migration runs cleanly. If migration fails: - Show the error - Check for conflicting model names, duplicate fields, or missing relations - Fix and re-run ## Step 4 — Output ``` Model scaffolded: $ModelName Schema: apps/api/prisma/schema.prisma Migration: apps/api/prisma/migrations/[timestamp]_add-$MODEL_SLUG/ Prisma client generated — TypeScript types are now available. Remember: - Binary (encrypted) salary fields are Uint8Array in TypeScript, NOT Buffer (Prisma 6) - Use P2025 error code when record not found (NotFoundError was removed in Prisma 6) - Monetary fields come back as Decimal type — wrap in new Decimal(value) for arithmetic Next: Add service layer and route, or run /impl:route "[resource]" "[method]" ```

{ "prompt": "> **Internal command.** Called by `/impl:story` automatically.\n\n> **Internal scaffolding command.** Called by story-orchestrator agents during /impl:story.\n> Not intended for direct user invocation.\n\nParse the argument:\n\n- `ModelName`: PascalCase model name (e.g., \"Enrollment\", \"StaffMember\", \"FiscalYear\")\n\nIf missing, ask the user: \"What is the name of the Prisma model you want to scaffold?\"\n\n## Step 1 — Invoke Skill\n\nUse the Skill tool to invoke: `prisma-model`\n\nThis skill handles all model scaffolding with correct BudFin patterns (Uint8Array for binary\nfields, DECIMAL(15,4) for monetary fields, P2025 error handling). Follow the skill exactly.\n\n## Step 2 — Verify Schema Updated\n\nAfter the skill writes to `apps/api/prisma/schema.prisma`:\n\n1. Read the schema file and confirm the new model block exists\n2. Verify field types follow BudFin conventions:\n - Monetary fields: `Decimal` (maps to `DECIMAL(15,4)`)\n - Encrypted salary fields: `Bytes` (maps to `Uint8Array` in TypeScript — Prisma 6)\n - IDs: `String @id @default(uuid())`\n - Timestamps: `DateTime @default(now())` / `DateTime @updatedAt`\n\n## Step 3 — Generate and Migrate\n\n```bash\npnpm --filter @budfin/api exec prisma generate\n```\n\nConfirm generation succeeds (zero errors).\n\n```bash\npnpm --filter @budfin/api exec prisma migrate dev --name add-$MODEL_SLUG\n```\n\nWhere `$MODEL_SLUG` is the lowercase kebab-case of the model name.\nExample: \"StaffMember\" → `add-staff-member`\n\nConfirm the migration runs cleanly.\n\nIf migration fails:\n\n- Show the error\n- Check for conflicting model names, duplicate fields, or missing relations\n- Fix and re-run\n\n## Step 4 — Output\n\n```\nModel scaffolded: $ModelName\n\nSchema: apps/api/prisma/schema.prisma\nMigration: apps/api/prisma/migrations/[timestamp]_add-$MODEL_SLUG/\n\nPrisma client generated — TypeScript types are now available.\n\nRemember:\n - Binary (encrypted) salary fields are Uint8Array in TypeScript, NOT Buffer (Prisma 6)\n - Use P2025 error code when record not found (NotFoundError was removed in Prisma 6)\n - Monetary fields come back as Decimal type — wrap in new Decimal(value) for arithmetic\n\nNext: Add service layer and route, or run /impl:route \"[resource]\" \"[method]\"\n```", "variables": [], "notes": "Scaffold a Prisma 6 model for BudFin using the prisma-model skill. Generates the model block with correct field types, relations, and Prisma 6 patterns (Uint8Array binary fields, P2025). Runs prisma generate and prisma migrate dev after scaffolding. Usage - /impl:model \"[ModelName]\" Tools: Bash, Read, Write, Edit, Skill. Arguments: \"[ModelName]\".", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/helalifaker/budfin", "path": ".codex/prompts/impl.model.md", "ref": "0ae459d12324d9c929baa7b09f783f5bc53911c6", "url": "https://github.com/helalifaker/budfin/blob/0ae459d12324d9c929baa7b09f783f5bc53911c6/.codex/prompts/impl.model.md", "key": "helalifaker/budfin/.codex/prompts/impl.model.md" } } }

impl:model

About

Step 1 — Invoke Skill

Step 2 — Verify Schema Updated

Step 3 — Generate and Migrate

Step 4 — Output

Install impl:model and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews