AI agents and editors
Load the EximAgent skill into a coding agent so it drives the CLI for you, and keep it inside a sandbox that still has egress.
EximAgent is designed to be driven by a coding agent as much as by a person. The installer sets this up automatically — the interesting part is knowing what the agent has been told.
The skill
The installer writes the EximAgent skill into the skill directories of coding agents it finds on the machine. The skill teaches the agent the intent map, which commands cost money, the preview-first doctrine, and how to read the confidence and coverage envelopes.
Load or inspect it directly at cli.eximagent.ai/skill. It is the always-current command reference — this documentation orients, the skill is authoritative.
What the agent is expected to do
- Ground in
profile getbefore acting on a vague request - Ask one concrete question rather than inventing a product, country, or HS code
- Preview billable steps with
--dry-runand show you the cost first - Batch lists through
--inputsinstead of looping - Never speak above a field's confidence tier
- Block on the stream before reading results
If an agent skips the shortlist step and enriches an entire result set, stop it. That is the failure mode that costs real money.
Sandboxing
The CLI needs outbound HTTPS. The correct configuration grants egress while keeping isolation on — for example, a workspace-write sandbox with network access enabled, rather than an unsandboxed run.
If egress cannot be granted, use the hosted MCP server instead. It needs no sandbox change because it connects from the host, not from inside the sandbox.
Reading results back into context
Bulk results belong on disk, not in an agent's context window. Use
--out <file> for exports, analyse the file with code, and read back only the
computed aggregates. See
bulk input and streaming.