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 mracal/vibe-engineering --skill service-health-dashboardgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/service-health-dashboard)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/service-health-dashboard"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/service-health-dashboard/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/mracal/vibe-engineering/service-health-dashboard"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/service-health-dashboard.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.00032 | $0.00490 |
| Opus 5 | $0.00016 | $0.00245 |
| Sonnet 5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
vibe-service-health-dashboard 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 12d 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.
This is a copy
100% identical to vibe-service-health-dashboard — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-service-health-dashboard
Know what's running, what's crashed, and what's about to crash.
When to Use This Skill
- Checking service health after deployment
- Investigating performance or availability issues
- Morning standup health check
- After infrastructure changes
When NOT to Use This Skill
- No services running (pure library/CLI project)
- Already have a monitoring dashboard (Grafana, Datadog, etc.)
- Development-only local services that don't need monitoring
Steps
-
Discover services — Check for:
- systemd:
systemctl --user list-units --type=service --state=running - Docker:
docker ps - PM2:
pm2 list - Kubernetes:
kubectl get pods
- systemd:
-
For each service, collect:
- Status (running/stopped/crashed)
- Uptime
- Last restart time and reason
- Recent error count (from logs)
- Resource usage (CPU, memory) if available
-
Identify issues:
- Crashed services (not running when expected)
- High-restart services (restarted >3 times recently)
- Resource-hungry processes (>80% CPU or memory)
- Error spikes (more errors than usual)
-
Provide remediation commands for each issue
Output Format
Service Health Dashboard
Services: X running, Y stopped, Z error Overall: HEALTHY / DEGRADED / CRITICAL
| Service | Status | Uptime | Restarts | Errors (1h) | CPU | Memory |
|---|---|---|---|---|---|---|
| api | ✓ Running | 3d 4h | 0 | 2 | 15% | 256MB |
| worker | ✗ Crashed | - | 5 | 38 | - | - |
Issues
- worker crashed — Last error: "OOM killed"
- Fix:
systemctl --user restart workeror increase memory limit
- Fix:
Recommended Actions
- [Action with command]
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.
- 12d ago First seen · 65 lines · 32 tokens per session scan A 555abf9a4fe5
vibe-service-health-dashboard is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 490 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-service-health-dashboard, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
agent-resource-allocator
Agent skill for resource-allocator - invoke with $agent-resource-allocator.
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
moai-platform-deployment
Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
multi-service-orchestration
PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.