Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/flowllm-ai/flowllm/remote_clientnpx skills add FlowLLM-AI/flowllm --skill remote_clientgit clone --depth 1 https://github.com/FlowLLM-AI/flowllmWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/flowllm-ai/flowllm/remote_client)<a href="https://agentmods.dev/skills/flowllm-ai/flowllm/remote_client"><img src="https://agentmods.dev/badge/skills/flowllm-ai/flowllm/remote_client.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00082 | $0.00879 |
| Opus 5 | $0.00041 | $0.00439 |
| Sonnet 5 | $0.00016 | $0.00176 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
remote-client scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Client
Overview
Use the FlowLLM lite remote_client flow to call a running remote_server over HTTP. Prefer it when work should execute on a configured remote project host instead of the local Codex shell.
The implementation lives in flowllm/lite/flow/remote_client_flow.py; the paired server endpoints live in flowllm/lite/flow/remote_server_flow.py.
Before Running
Confirm the target host and port before launching remote work:
fl --remote-client --action ping
If --host is omitted, remote_client_flow.py reads DEFAULT_REMOTE_HOST_ENV. If neither is set, it raises Remote host is required. Set DEFAULT_REMOTE_HOST_ENV or pass --host.
Use --host only when overriding DEFAULT_REMOTE_HOST_ENV. Use --port only when the server is not on the default 8765.
Actions
Run a shell command remotely and stream stdout/stderr back to the local terminal:
fl --remote-client --action exec --command "pytest tests/unit"
Run a command stored in a local file:
fl --remote-client --action exec --command-file /path/to/command.sh
Upload and run a local Python file on the remote server:
fl --remote-client --action exec --python-file /path/to/script.py
Inspect tracked remote tasks:
fl --remote-client --action tasks
fl --remote-client --action tasks --status running --tail 80
Terminate a task or all running tasks:
fl --remote-client --action kill --task-id 12
fl --remote-client --action kill_all
Parameters
--action: one ofexec,ping,tasks,kill,kill_all; default isexec.--host: remote host. Falls back toDEFAULT_REMOTE_HOST_ENV.--port: remote server port; default is8765.--timeout: command timeout in seconds; default is3600.--command: shell command string forexec.--command-file: local text file whose contents become the remote shell command.--python-file: local Python file uploaded as code and run by the remote Python interpreter.--status: optional task status filter fortasks, commonlyrunning,finished, orkilled.--tail: output lines to include per task fortasks; default is30.--task-id: required forkill.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 100 lines · 82 tokens per session scan A 66b4aed1b906
remote-client is a skill published in the GitHub repository FlowLLM-AI/flowllm (34 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 879 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
intelliconnect-service-style
Create or update IntelliConnect Spring Boot service/serviceimpl code in this repository style. Use when adding backend services, service implementations, request DTOs, repository methods, CRUD methods, token-filtered get methods, SafetyService-bound permission boundaries, duplicate checks, dependency checks before…
umg-mcp-authoring
Use when Codex needs to create, edit, inspect, validate, or demo UE5.8 UMG interfaces through Unreal Motion Graphics MCP/FabUmgMcp, especially target/default workflows, widget tree authoring, HLSL-backed UI materials, Sequencer widget animations, Blueprint event wiring, readback validation, or operation-trace demo…
umg-material-mcp
Use when Codex needs to create, inspect, edit, delete, or validate UE5.8 material assets through Unreal Motion Graphics MCP/FabUmgMcp HLSL material tools, especially one-HLSL Custom-node authoring, UI-default versus non-UI material type selection, union-only writes, semantic outputs, hlsldelete recovery, or Material…
c-03-repo-bootstrap
Bootstrap onboarding for undocumented repos or existing memory slices. Builds root overviews, route-local overview pillars, evidence packs, file cards, onboarding waves, deleted-slice cleanup, curator reviews, and handoff while keeping the orchestrator thin.
c-12-closeout
Close out approved Agents Remember edits by preserving approval authority, mandatory strict code quality before code commit, missing-onboarding checks, external-memory refresh, memory quality, ledger alignment, and no automatic push.
l-01-agent-lifecycles
The agent lifecycles: one lifecycle per agent type, under one roof. Routes every session by exactly three conditions (spawn-role env -> fresh role brief -> otherwise free-chat launcher), carries the minimal lifecycle frame (the six lifecycle signals every session shares), and houses the self-contained per-role…