add-server

An interactive command for adding a server to a fleet-management inventory. It checks whether a server profile already exists before changing anything.

In plain words
What is it for?
Use it to add a new server, activate an existing profile, or update only connection and newly discovered server information.
Why use it?
It helps prevent accidental overwrites that could erase saved permissions, protected resources, or notes.

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/add-server
Clone the repo
git clone --depth 1 https://github.com/CallMeTechie/fleet-manager
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 494 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.00019 $0.00494
Opus 5 $0.00010 $0.00247
Sonnet 5 $0.00004 $0.00099
Haiku 4.5 $0.00002 $0.00049

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

Security

Grade A, and why

add-server 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/add-server.md · 46 lines

What it actually says

Add Server

set -euo pipefail
source "${CLAUDE_PLUGIN_ROOT:-plugin}/commands/_fleet-lib.sh"
mkdir -p "$FM_SERVERS_DIR"
NAME="$(printf '%s' "$ARGUMENTS" | tr -d '[:space:]')"
if [ -n "$NAME" ] && profile_exists "$NAME"; then
  echo "RE_ADD: server '$NAME' already exists"
fi

Re-Add protection (Concern 1): If the script prints RE_ADD: …, the server already exists. Do not overwrite it blindly (that would lose Scoped Operations, Protected Resources and Notes). Ask the user via AskUserQuestion: "Server <name> existiert. Was tun?" → Options:

  • "Aktiv setzen (/use)" → run set_active <name>; write_inventory and stop.
  • "Update-Modus" → update only the Connection section + newly discovered Identity/Discovered-State fields; preserve Scoped Operations, Protected Resources and Notes.
  • "Abbrechen".

Otherwise (new server): run the intake dialogue from /first-run step 1 yourself, here in the main thread, then dispatch the fleet-intake subagent with the collected values exactly as /first-run step 2 describes, and handle its return value as /first-run step 3 describes.

The subagent has no AskUserQuestion tool — subagents cannot reach the user — so it must never be dispatched before every answer is in hand.

Two differences from /first-run:

  • The inventory is not empty, so <name> must not collide with an existing profile. The bash block above already reports a collision for an argument-supplied name; re-check with profile_exists after the dialogue if the user typed a different one.
  • Do not assume the new server should become active. Dispatch with set_active=no, then ask via AskUserQuestion after a successful intake, and only run set_active <name>; write_inventory if the user says yes.
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 · 46 lines · 19 tokens per session scan A cb8538e546c6

Subscribe to this mod's changes

add-server is a command published in the GitHub repository CallMeTechie/fleet-manager (1 stars, last pushed 29d ago), licensed MIT. It adds 19 tokens to every session and 494 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.