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 ash1794/vibe-engineering --skill service-health-dashboardgit clone --depth 1 https://github.com/ash1794/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/ash1794/vibe-engineering/service-health-dashboard)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/service-health-dashboard"><img src="https://agentmods.dev/badge/skills/ash1794/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/ash1794/vibe-engineering/service-health-dashboard"><img src="https://agentmods.dev/badge/skills/ash1794/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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-service-health-dashboard — 100% identical, 0 lines differ
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 ash1794/vibe-engineering (10 stars, last pushed 3mo ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
resolve-plugins
Curate Claude Code skill / MCP / hook picks against live upstream sources and pin them in .claude/settings.json. Adding a process harness (a paired skill set) is an ordinary pick this door handles. Reads stack from docs/techstack.md, workflow signal from docs/overview.md + existing pins, then live-queries six source…
engine-bootstrap
Use when no contextualizer exists yet for a set of source URLs or local paths and one needs to be scaffolded from scratch.
refresh
Use when an existing contextualizer's references may have drifted from current upstream state — typically weekly, or whenever a few days of upstream changes have accumulated — to bring them back into agreement.
using-skill-engine
When the user mentions skill-engine or "the engine" without naming a specific workflow, or wants first-run setup. Inspects .claude/skills/-context/ install state (and any pending -context.proposed/ proposals) across all three install levels, then dispatches to engine-bootstrap when no contextualizer exists, to…
apply
Use when a staged proposal has been reviewed and signed off — REVIEW.md Step 3 ticked reviewed or provisional — and is ready to promote into the live contextualizer.
config-set
Use when changing an engine-wide config value — currently diff.tool, the command /skill-engine:review prints for inspecting a proposed-vs-live diff.