list-servers

An inventory command that lists every server recorded in the fleet manager and marks the currently active one. It also regenerates the inventory file.

In plain words
What is it for?
Use it to check which servers are configured and which one is selected for current operations.
Why use it?
It gives you a current view of the servers available to the other commands and makes the active server clear.

Command

Install

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.

agentmods
npx agentmods add commands/callmetechie/fleet-manager/list-servers
Clone the repo
git clone --depth 1 https://github.com/CallMeTechie/fleet-manager
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 130 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00130
Opus 5 $0.00010 $0.00065
Sonnet 5 $0.00004 $0.00026
Haiku 4.5 $0.00002 $0.00013

Measured 2d ago against content hash 1b36b11a1e2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

list-servers 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 2d 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.

plugin/commands/list-servers.md · 22 lines

What it actually says

List servers

set -euo pipefail
source "${CLAUDE_PLUGIN_ROOT:-plugin}/commands/_fleet-lib.sh"

if [ -z "$(list_server_names)" ]; then
  echo "Inventory is empty. Run /first-run to onboard your first server."
  exit 0
fi

write_inventory
cat "$FM_CONTEXT/inventory.md"

Display the table to the user. The * in the Active column marks the active server.

Changes

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.

  1. 2d ago First seen · 22 lines · 20 tokens per session scan A 1b36b11a1e2e

Subscribe to this mod's changes

list-servers is a command published in the GitHub repository CallMeTechie/fleet-manager (1 stars, last pushed 29d ago), licensed MIT. It adds 20 tokens to every session and 130 once invoked, about $0.0001 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-31.