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 skills add S3YED/appie-kit --skill agent-fleet-operationsgit clone --depth 1 https://github.com/S3YED/appie-kitWrote 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/s3yed/appie-kit/agent-fleet-operations)<a href="https://agentmods.dev/skills/s3yed/appie-kit/agent-fleet-operations"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/agent-fleet-operations.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.1 | $0.00034 | $0.01740 |
| Opus 5 | $0.00017 | $0.00870 |
| Sonnet 5 | $0.00007 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
agent-fleet-operations 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 6d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Fleet Operations
Use this skill when operating Hermes-style agents across one or more machines: bootstrapping a new node, refreshing an agent kit or knowledge pack, validating remote access, troubleshooting remote deploy failures, or recovering Hermes provider/gateway failures that prevent the agent from answering.
This is an umbrella skill. It absorbs the former fleet-provisioning and hermes-provider-troubleshooting skills. Load the protected hermes-agent skill first for authoritative Hermes CLI/config commands, then use this skill for fleet-level operational sequence and operator-specific lessons.
Core operating model
Treat each layer as a separate gate:
- Identity and ownership: which machine, account, Tailnet name/IP, and runtime profile are in scope?
- Network visibility: can the node be reached on the overlay or public network?
- Transport access: are SSH/VNC/HTTP control-plane ports open independently?
- Authentication: does the intended user/key/token actually work?
- Configuration: does Hermes point at the intended provider/model/runtime paths?
- Credentials and quota: are provider credentials fresh, scoped to this node, and not exhausted?
- Runtime readiness: is the gateway/service restarted and answering after changes?
- Artifact verification: did the files, knowledge pack, persona, or service entrypoint land where expected?
Do not collapse these gates. A node can answer Tailscale ping while refusing SSH. SSH port 22 can be open while public-key auth fails. Hermes config can be correct while OAuth is stale or quota is exhausted.
Remote provisioning workflow
Use for bootstrapping or refreshing remote agent hosts, Macs, VPS nodes, or Tailnet-hosted agents.
- Confirm target identity, owner, and intended user.
- Check Tailnet or network reachability.
- Check each required control-plane port separately.
- Prove shell access with a harmless command before running deploy scripts.
- Run deploy scripts in dry-run mode if available.
- Only then copy files, rsync knowledge packs, install services, or write persona/runtime files.
- Verify installed files and runtime entrypoints on the target.
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.
- 6d ago First seen · 164 lines · 34 tokens per session scan A 441fdbd27ff0
agent-fleet-operations is a skill published in the GitHub repository S3YED/appie-kit (7 stars, last pushed 11d ago), licensed MIT. It adds 34 tokens to every session and 1,740 once invoked, about $0.0002 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.
Other skills, from other repositories
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
aws-patterns
Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
agents-md-protocol
Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.
impact-report-writer
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.