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 agentmods add skills/softspark/ai-toolkit/healthnpx skills add softspark/ai-toolkit --skill healthgit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/health)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/health"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/health.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.00037 | $0.00920 |
| Opus 5 | $0.00018 | $0.00460 |
| Sonnet 5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
health scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| HTTP API | `curl -f http://localhost:{port}/health` | How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health Check
$ARGUMENTS
Check the health of all project services.
Project context
- Services: !
docker compose ps 2>/dev/null || echo "no-docker"
Auto-Detection
Detect services from docker-compose.yml, .env, or project configuration.
Quick Check
# If using Docker Compose
docker compose ps
# Process check (bare metal)
ps aux | grep -E "(node|python|java|php)" | grep -v grep
Common Service Checks
| Service | Health Check |
|---|---|
| HTTP API | curl -f http://localhost:{port}/health |
| PostgreSQL | pg_isready -h localhost -p 5432 |
| MySQL | mysqladmin ping -h localhost |
| Redis | redis-cli ping |
| MongoDB | mongosh --eval "db.runCommand({ping:1})" |
| Elasticsearch | curl -f http://localhost:9200/_cluster/health |
| RabbitMQ | curl -f http://localhost:15672/api/healthchecks/node |
Diagnostics
# Container logs (if Docker)
docker compose logs --tail 50 {service}
# Resource usage
docker stats --no-stream # Docker
htop # Bare metal
# Disk usage
df -h # System
docker system df # Docker
# Network
netstat -tlnp # Listening ports
curl -I http://localhost:{port} # Connectivity
Common Issues
| Symptom | Check | Solution |
|---|---|---|
| Service not responding | Process running? Port open? | Restart service |
| Slow responses | Resource usage, connections | Scale or optimize |
| Connection refused | Network, firewall, port | Check config |
| Out of memory | free -h, container limits |
Increase limits |
Automated Health Check
Run the bundled script for a JSON health report:
python3 ${CLAUDE_SKILL_DIR}/scripts/health_check.py http://localhost:8000
Health Report Format
services:
{service-name}:
status: healthy|degraded|down
uptime: Xd Xh
cpu: X%
memory: XMB
notes: "any issues"
Rules
- MUST report measured values — never mark a service healthy without a successful probe
- NEVER restart a degraded service without the user's explicit go-ahead
- CRITICAL: separate liveness (process up) from readiness (accepting traffic) in the report
- MANDATORY: if a health endpoint times out, classify as
degraded, nothealthy
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 113 lines · 37 tokens per session scan A 939bd48f0ae4
health is a skill published in the GitHub repository softspark/ai-toolkit (169 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 920 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
k8s-deploy
Deploy and manage applications on Kubernetes clusters with kubectl and Helm.
odoo-docker-deployment
Production-ready Docker and docker-compose setup for Odoo with PostgreSQL, persistent volumes, environment-based configuration, and Nginx reverse proxy.
k8s
Kubernetes and container orchestration skill. Helm charts, deployment strategies (rolling, canary, blue-green), pod health, resource limits, scaling. Triggers on: /godmode:k8s, "deploy to kubernetes", "helm chart", "pod crashing", "OOMKilled".
roo-bedrock-custom-arn
Roo Code's Bedrock provider silently disables caching for custom ARNs. Populate cachableFields to fix.
frappe-ops-deployment
Use when deploying Frappe/ERPNext to production, configuring Nginx or Supervisor, setting up Docker, enabling SSL, or hardening security. Prevents insecure deployments, missing reverse proxy config, and broken process management. Covers production setup, Nginx configuration, Supervisor/systemd, Docker Compose, Let's…
kubernetes-ops
Kubernetes operations including deployments, services, HPA, RBAC, debugging, Helm charts, and cluster management. Trigger when users deploy to Kubernetes, debug pod issues, configure scaling, set up RBAC, or write Helm charts.