Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AutoResearch-Factory/Agon/plugin install agonWrote 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/autoresearch-factory/agon/server-health)<a href="https://agentmods.dev/skills/autoresearch-factory/agon/server-health"><img src="https://agentmods.dev/badge/skills/autoresearch-factory/agon/server-health/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/autoresearch-factory/agon/server-health"><img src="https://agentmods.dev/badge/skills/autoresearch-factory/agon/server-health.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.00034 | $0.00231 |
| Opus 5 | $0.00017 | $0.00115 |
| Sonnet 5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
server-health 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 11d 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
Server health snapshot
Placeholder for project-specific compute availability.
This release intentionally ships no private server names, accounts, paths, queues, credentials, or monitoring scripts. Projects should fill references/servers_manual.md or replace this skill with their own health collector.
Usage Contract
- First read
${CLAUDE_PLUGIN_ROOT}/references/servers_manual.md. - Use only project-provided server labels, paths, queues, and monitoring commands.
- If the project has not configured compute resources, report
UNKNOWNand ask the user for server information. - Do not guess private hostnames, usernames, storage roots, queues, or GPU availability.
Expected Project Notes
The server manual should define:
- host labels and access method
- GPU/CPU/RAM inventory
- scheduler or launch rules
- canonical remote project root
- dataset/cache/checkpoint/result locations
- how to check load, jobs, disk, and running experiments
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.
- 11d ago First seen · 29 lines · 34 tokens per session scan A 1af3391b3c6b
server-health is a skill published in the GitHub repository AutoResearch-Factory/Agon (47 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 231 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-30.
Other skills, from other repositories
multi-service-orchestration
PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.
check-deployment-status
Check the health and sync status of all ArgoCD applications across clusters. Identifies out-of-sync, degraded, or unhealthy deployments and provides actionable remediation steps. Use when monitoring deployments, troubleshooting sync failures, or verifying environment health after a release.
cluster-resource-health
Check Kubernetes cluster health including pod status, node conditions, resource utilization, and pending alerts across EKS clusters. Use when monitoring infrastructure health, investigating capacity issues, or performing cluster audits.
ledger
Optimizing FinOps and cloud cost: IaC-based estimation, right-sizing, RI/SP recommendations, anomaly detection, budget alerts, AI/GPU workload economics. Use to forecast or cut cloud spend.
scaffold
Provisioning infrastructure via cloud IaC (Terraform/OpenTofu/CloudFormation/Pulumi) and local dev environments (Docker Compose, env vars). Use for IaC design or multi-cloud provisioning.
diagram-architecture
Dark-themed SVG architecture/cloud/infra diagrams as HTML.