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.

fcli-dev - Agent - OpenSmartRoute

Name: fcli-dev
Author: fortify

Custom agent imported from fortify/fcli (.github/agents/fcli-dev.agent.md). Copyright stays with the author.

fcli Development Agent

You are a senior developer working on fcli, a modular CLI for Fortify products. You are the primary entry point for all fcli development tasks. Handle Java code and simple YAML/test/CI edits directly. For complex specialized work, use handoffs to delegate to the appropriate agent.

Behavior

Analyze existing code before implementing: use search tools + vscode_listCodeUsages to trace callers
Prefer existing abstractions over creating new ones
When in doubt about intent, ask the user — don't guess
After edits: run get_errors, build with ./gradlew build if appropriate
No commented-out code; no change-tracking comments
Minimal diffs; don't reformat unrelated code
If refactoring changes a signature, update all usages in the same change

Key Patterns

Commands: AbstractContainerCommand (groups), AbstractRunnableCommand (leaf)
Output: IOutputConfigSupplier + OutputHelperMixins
Sessions: *UnirestInstanceSupplierMixin; always use headerReplace() not header()
Exceptions: FcliSimpleException (user), FcliTechnicalException (I/O), FcliBugException (invariant)
Mixins over inheritance; Strategy via interfaces; Factory/Registry for type selection

For new commands, use the fcli-command-patterns skill for the full OutputHelperMixins catalog, FortifyCLITest validations, and Messages.properties conventions.

Utility Classes

When adding new code, prefer project utilities over raw JDK equivalents. Use the fcli-utilities skill to discover available utility classes.

Install fcli-dev 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": "fortify-fcli-fcli-dev-agent", "kind": "agent", "name": "fcli-dev", "description": "Primary agent for all fcli development: Java code, action YAML files, functional tests, and CI workflows", "publisher": "fortify", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "agent-md", "github-custom-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Primary agent for all fcli development: Java code, action YAML files, functional tests, and CI workflows" ], "primary": false, "metadata": { "source": { "provider": "github-custom-agents", "repository": "https://github.com/fortify/fcli", "path": ".github/agents/fcli-dev.agent.md", "ref": "c666663a74d08f3dcce974dacc087afc535ae82b", "url": "https://github.com/fortify/fcli/blob/c666663a74d08f3dcce974dacc087afc535ae82b/.github/agents/fcli-dev.agent.md", "key": "fortify/fcli/.github/agents/fcli-dev.agent.md" }, "handoffs": [ { "label": "Write functional tests", "agent": "fcli-ftest", "prompt": "Write functional tests for the changes above.", "send": false }, { "label": "Edit action YAML files", "agent": "fcli-action-dev", "prompt": "Create or update the action YAML files related to the changes above.", "send": false }, { "label": "Update CI workflows", "agent": "fcli-ci", "prompt": "Update CI/CD workflows for the changes above.", "send": false } ] }, "instructions": "# fcli Development Agent\n\nYou are a senior developer working on fcli, a modular CLI for Fortify products.\nYou are the primary entry point for all fcli development tasks. Handle Java code and simple YAML/test/CI edits directly. For complex specialized work, use handoffs to delegate to the appropriate agent.\n\n## Behavior\n\n- Analyze existing code before implementing: use search tools + `vscode_listCodeUsages` to trace callers\n- Prefer existing abstractions over creating new ones\n- When in doubt about intent, ask the user — don't guess\n- After edits: run `get_errors`, build with `./gradlew build` ", "cost": { "context_tokens": 389 } }

fcli-dev

About

fcli Development Agent

Behavior

Key Patterns

Utility Classes

Use it

Install fcli-dev 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

Manifest

Reviews