fulcra-agent-atc

Routes agent tasks to the cheapest capable model across subscription accounts using a shared cap ledger.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-atc-ashfulcra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fulcra-agent-atc
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/fulcra-agent-atc
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-atc-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fulcra-api, coord-engine.

What problem does it solve? Teams running multiple AI subscriptions waste frontier-model budget on mechanical work and stall when one account hits its rate cap while others sit idle. This Skill provides a routing layer that picks the cheapest capable model with headroom and keeps a shared ledger of usage across accounts. ## Core Features & Use Cases - Capability-ranked routing: coord-engine route --needs code,long-context ranks models cheapest-capable-first, filtered to accounts with current headroom, using a frozen capability taxonomy (code, architecture, writing, long-context, vision, fast, tool-use). - Cross-account cap ledger: declared rolling windows per account track spend; a real throttle event zeroes that account's headroom for the window and flags it for cap calibration. - Outcome-driven demotion: logging --model --task-class --outcome demotes a (model, task_class) pair after repeated rework/escalated outcomes, so the router stops picking models that keep failing a task class. - Use Case: A coordinator agent on a multi-harness team needs code review done; it runs route --needs code, dispatches to the top-ranked model on the account with headroom, and logs the outcome so the fleet ledger stays honest. ## Quick Start Install the fulcra and coord-engine CLIs, run coord-engine atc init to declare your subscription accounts, then ask the agent to route a task with coord-engine route solo --needs code before dispatching it.

Frequently Asked Questions about fulcra-agent-atc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route an agent task to the cheapest capable model?▼

Run `coord-engine route <team> --needs <tags>` with capability tags like code or long-context. The router ranks models cheapest-capable-first among accounts with current headroom, and you take rank 1 unless a candidate is marked demoted.

How do I avoid hitting subscription rate limits across multiple AI accounts?▼

Declare each account's rolling windows in accounts.json and log every dispatch with `coord-engine usage log`. The shared headroom ledger shows remaining capacity per window, and a real throttle event zeroes that account until the window rolls over.

Does this model router work with a single account or only fleets?▼

It works standalone on one account with team defaulting to solo. Fleet features like cross-harness dispatch, role bindings, and harvest of review outcomes only activate when you run it on a coord team with multiple harnesses.

What happens when a model keeps failing a type of task?▼

When a (model, task_class) pair has at least 3 outcome-bearing shards and 3 of its trailing 5 are rework or escalated, the router demotes it. Demoted candidates sort below all healthy ones until later clean outcomes restore them.

Why does route return no candidates for my task?▼

This happens when all accounts are near their caps or throttled. Either degrade the needs (drop architecture and use a lower tier), defer work past the window boundary, or declare an uncapped local account like ollama as a fallback lane.