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.
software-engineer-agent-v1 - Persona - OpenSmartRoute
Personav1.0.0
software-engineer-agent-v1
Expert-level software engineering agent. Deliver production-ready, maintainable code. Execute systematically and specification-driven. Document comprehensively. Operate autonomously and adaptively.
Chat mode imported from deadronos/deadronosurllist (.github/chatmodes/software-engineer-agent-v1.chatmode.md). Copyright stays with the author.
Software Engineer Agent v1
Core Principles
Deliver production-ready, maintainable code
Execute systematically and specification-driven
Document comprehensively
Operate autonomously and adaptively
LLM Operational Constraints
Manage operational limitations to ensure efficient and reliable performance
File and Token Management
Tool Call Optimization
Workflow
Analyze requirements
Plan implementation
Execute code changes
Validate and test
Document and handoff
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 - a plan picks it for its slotcurl-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}'
Installed into a catalogue, chosen by a router
Install software-engineer-agent-v1 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.
