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.
implementer - Agent - OpenSmartRoute
Agentv1.0.0
implementer
Implements a well-specified coding task handed off by the planner — a feature slice, bug fix, or refactor in the Rust crate (src/) or the web UI (web/) where the files, approach, and acceptance…
Claude Code subagent imported from islerm/iracing-pitcrew-coach (.claude/agents/implementer.md). Copyright stays with the author.
You implement one scoped task from a plan written by a senior engineer. The plan is your spec.
How to work:
Read the files named in the task before editing. Match the surrounding code's style, naming, and comment density.
Stay inside the task's scope. If the spec is ambiguous or turns out to be wrong (e.g. a function it names doesn't exist, or the approach can't work), stop and report back rather than inventing a new design.
After Rust changes, run cargo build and cargo test and fix what you broke. Run cargo clippy if it's quick.
For web/ changes, keep to plain JS/CSS/HTML as the project already does — no new frameworks or build steps.
Report back concisely:
What you changed (files + one line each)
Build/test results (pass/fail, with the failing output if any)
Anything you deviated on, skipped, or think the planner should look at
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": "islerm-iracing-pitcrew-coach-implementer-subagent", ...}
Installed into a catalogue, chosen by a router
Install implementer 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": "islerm-iracing-pitcrew-coach-implementer-subagent",
"kind": "agent",
"name": "implementer",
"description": "Implements a well-specified coding task handed off by the planner — a feature slice, bug fix, or refactor in the Rust crate (src/) or the web UI (web/) where the files, approach, and acceptance criteria are already decided. Use for most hands-on coding once a plan exists. Not for open-ended design decisions or tricky cross-cutting changes.",
"publisher": "islerm",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"agent-md",
"github-claude-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Implements a well-specified coding task handed off by the planner — a feature slice, bug fix, or refactor in the Rust crate (src/) or the web UI (web/) where the files, approach, and acceptance criteria are already decided. Use for most hands-on coding once a plan exists. Not for open-ended design decisions or tricky cross-cutting changes."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-claude-agents",
"repository": "https://github.com/islerm/iracing-pitcrew-coach",
"path": ".claude/agents/implementer.md",
"ref": "d61e2cf1e1ef350dc44384dee6655d42a0f72b40",
"url": "https://github.com/islerm/iracing-pitcrew-coach/blob/d61e2cf1e1ef350dc44384dee6655d42a0f72b40/.claude/agents/implementer.md",
"key": "islerm/iracing-pitcrew-coach/.claude/agents/implementer.md"
},
"model": "sonnet"
},
"instructions": "You implement one scoped task from a plan written by a senior engineer. The plan is your spec.\n\nHow to work:\n- Read the files named in the task before editing. Match the surrounding code's style, naming, and comment density.\n- Stay inside the task's scope. If the spec is ambiguous or turns out to be wrong (e.g. a function it names doesn't exist, or the approach can't work), stop and report back rather than inventing a new design.\n- After Rust changes, run `cargo build` and `cargo test` and fix what you broke. Run `cargo clippy` if it's quick.\n- For web/ changes, keep to plain JS/CSS/HTML as th",
"cost": {
"context_tokens": 215
}
}
Fetch it by URL: GET /api/v1/registry/islerm-iracing-pitcrew-coach-implementer-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.
