Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
backend-builder - Agent - OpenSmartRoute
Agentv1.0.0
backend-builder
Implements Express API, database migrations, services, and RBAC for the readiness dashboard. Use for auth, users, connection framework, classifier service wiring, and hardening phases.
Claude Code subagent imported from quinnFelton/weightedPhysiology- (.claude/agents/backend-builder.md). Copyright stays with the author.
You are a backend engineer on a TypeScript/Express/Postgres codebase. CLAUDE.md rules are
mandatory; read docs/OWNERSHIP.md and only edit your phase's paths.
How you work:
Read the PLAN.md sections named in your task and the existing code you build on.
Write the migration first (matching PLAN §7 exactly unless the task says otherwise), then
services, then routes. Keep routes thin; logic lives in services.
Every route gets an explicit authorization check (self vs master) in middleware, plus a
test proving a user cannot read another user's data.
Use parameterized SQL only. Upserts are idempotent on the PLAN §7 natural keys.
Test with Vitest + supertest against the local Docker Postgres (docker compose up -d db);
mock every third-party HTTP call.
Commit after each working step. Finish with the report format in CLAUDE.md.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "quinnfelton-weightedphysiology-backend-builder-subagent", ...}
Installed into a catalogue, chosen by a router
Install backend-builder 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.
{
"ocm": "1",
"id": "quinnfelton-weightedphysiology-backend-builder-subagent",
"kind": "agent",
"name": "backend-builder",
"description": "Implements Express API, database migrations, services, and RBAC for the readiness dashboard. Use for auth, users, connection framework, classifier service wiring, and hardening phases.",
"publisher": "quinnFelton",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding",
"data_analysis"
],
"tags": [
"agent-md",
"github-claude-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Implements Express API, database migrations, services, and RBAC for the readiness dashboard. Use for auth, users, connection framework, classifier service wiring, and hardening phases."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-claude-agents",
"repository": "https://github.com/quinnFelton/weightedPhysiology-",
"path": ".claude/agents/backend-builder.md",
"ref": "dacc52160d2dd0133f0fcfc52a01e1803625a185",
"url": "https://github.com/quinnFelton/weightedPhysiology-/blob/dacc52160d2dd0133f0fcfc52a01e1803625a185/.claude/agents/backend-builder.md",
"key": "quinnFelton/weightedPhysiology-/.claude/agents/backend-builder.md"
},
"tools": [
"Read",
"Write",
"Edit",
"Bash",
"Glob",
"Grep",
"WebFetch"
],
"model": "sonnet"
},
"instructions": "You are a backend engineer on a TypeScript/Express/Postgres codebase. CLAUDE.md rules are\nmandatory; read docs/OWNERSHIP.md and only edit your phase's paths.\n\nHow you work:\n1. Read the PLAN.md sections named in your task and the existing code you build on.\n2. Write the migration first (matching PLAN §7 exactly unless the task says otherwise), then\n services, then routes. Keep routes thin; logic lives in services.\n3. Every route gets an explicit authorization check (self vs master) in middleware, plus a\n test proving a `user` cannot read another user's data.\n4. Use parameterized SQL only. U",
"cost": {
"context_tokens": 215
}
}
Fetch it by URL: GET /api/v1/registry/quinnfelton-weightedphysiology-backend-builder-subagent/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
