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.
git clone --depth 1 https://github.com/CallMeTechie/fleet-managerWrote 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/plugins/callmetechie/fleet-manager/plugin)<a href="https://agentmods.dev/plugins/callmetechie/fleet-manager/plugin"><img src="https://agentmods.dev/badge/plugins/callmetechie/fleet-manager/plugin/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/callmetechie/fleet-manager/plugin"><img src="https://agentmods.dev/badge/plugins/callmetechie/fleet-manager/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fleet-manager 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 1mo 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.
What it actually says
{
"name": "fleet-manager",
"version": "0.3.4",
"description": "Multi-server SSH management for Claude Code. Inventory of servers with an active-server model, guided setup, SSH key deployment, connectivity diagnostics, and system status across a fleet of Linux hosts.",
"author": { "name": "CallMeTechie", "url": "https://github.com/CallMeTechie" },
"homepage": "https://github.com/CallMeTechie/fleet-manager",
"repository": "https://github.com/CallMeTechie/fleet-manager",
"license": "MIT",
"keywords": ["ssh", "fleet", "sysadmin", "multi-server", "remote", "monitoring", "docker", "compose"]
}
What it installs
The manifest is a name and a version. 1 skill, 17 commands, 1 agent travel with it, and installing the plugin installs all of them — 492 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill fleet-manager A 51 tokens
- Command compose-down A 33 tokens
- Command compose-up A 38 tokens
- Command copy A 33 tokens
- Command first-run A 14 tokens
- Command sync A 30 tokens
- Command add-server A 19 tokens
- Command compose-update A 27 tokens
- Command logs A 29 tokens
- Command compose-logs A 13 tokens
- Command docker-list A 22 tokens
- Command health-summary A 23 tokens
- Command use A 17 tokens
- Command compose-list A 20 tokens
- Command status A 18 tokens
- Command list-servers A 20 tokens
- Command setup-ssh B 23 tokens
- Command diag B 25 tokens
- Agent fleet-intake B 37 tokens
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.
- 1mo ago First seen · 11 lines scan A 759960213e58
fleet-manager is a plugin published in the GitHub repository CallMeTechie/fleet-manager (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
marina-skill
Claude Code skills for managing Hetzner servers, Cloudflare DNS, and Docker deployments.
systems-architecture
Systems architecture and distributed systems skills including Designing Data-Intensive Applications (Martin Kleppmann), System Design Interview (Alex Xu), Clean Architecture (Robert C. Martin), Release It! (Michael Nygard), High Performance Browser Networking (Ilya Grigorik), and Team Topologies (Skelton & Pais).
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG, App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker size/runtime/keepnames/FinalizationRegistry/connect.
cloudflare-queues
This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput exceeded".
cloudflare-browser-rendering
Cloudflare Browser Rendering with Puppeteer/Playwright. Use for screenshots, PDFs, web scraping, or encountering rendering errors, timeout issues, memory exceeded.
cloudflare-cron-triggers
Cloudflare Cron Triggers for scheduled Workers execution. Use for periodic tasks, scheduled jobs, or encountering handler not found, invalid cron expression, timezone errors.