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 phuonghx/aim-cli --skill server-managementgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/server-management)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/server-management"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/server-management/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/skills/phuonghx/aim-cli/server-management"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/server-management.svg" alt="Reviewed on agentmods" width="80" 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.00085 | $0.00963 |
| Opus 5.5 | $0.00034 | $0.00385 |
| Sonnet 5.5 | $0.00017 | $0.00193 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
server-management 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Servers in Production
Operations is a series of judgment calls, not a list of commands to memorize. The sections below help you reason from goals and symptoms to the right choice for your situation.
Keeping processes alive
Pick the supervisor that matches what you are running:
| Running | Reach for |
|---|---|
| A Node.js app | PM2 -- clustering and zero-downtime reloads |
| Any Linux service | systemd -- the native init |
| Containerized workloads | Docker or Podman |
| Many services together | Kubernetes or Docker Swarm |
Whatever you choose, it should deliver the same four things: restart automatically after a crash, reload without dropping requests, use every CPU core (clustering), and come back on its own after the host reboots.
Monitoring
Watch four families of signal:
| Family | Representative metrics |
|---|---|
| Availability | uptime, health-check status |
| Performance | latency, throughput |
| Errors | error rate, error types |
| Resources | CPU, memory, disk |
Tie each alert to a response so noise does not drown signal: critical means act now, warning means look into it soon, info means review on a normal cadence.
Match the tooling to the budget and need: PM2's built-in metrics or htop for something free and simple; Grafana or Datadog for full observability; Sentry for error tracking; UptimeRobot or Pingdom for external uptime checks.
Logs
Different logs answer different questions -- application logs for debugging and audit, access logs for traffic patterns, error logs for catching failures.
Four practices keep logging useful rather than harmful:
- Rotate logs so they never fill the disk.
- Emit structured logs (JSON) so they are machine-parseable.
- Use levels deliberately -- error, warn, info, debug.
- Never write secrets or sensitive data to a log.
Scaling
Read the symptom before reaching for a fix:
| Symptom | First move |
|---|---|
| CPU pinned | add instances (scale out) |
| Memory exhausted | add RAM, or hunt the leak |
| Responses slow | profile first, then scale |
| Spiky traffic | autoscaling |
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 · 106 lines · 85 tokens per session scan A 7f0655da46b9
server-management is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 85 tokens to every session and 963 once invoked, about $0.0003 per session on Opus 5.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
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
web-platform-baseline
Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale knowledge be stated as current. Triggers: user says "container query", "can I use", "browser support", "modern CSS", ":has"…
doc-coauthoring
Collaboratively author technical specifications, RFCs, PRDs, ADRs, and decision documents through structured context gathering, iterative refinement, and blind reader testing. Use when drafting substantial documentation, architecture proposals, or engineering design records.