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 LambdaTest/agent-skills --skill api-health-monitoringgit clone --depth 1 https://github.com/LambdaTest/agent-skillsWrote 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/lambdatest/agent-skills/api-health-monitoring)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/api-health-monitoring"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/api-health-monitoring/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/lambdatest/agent-skills/api-health-monitoring"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/api-health-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00156 | $0.01450 |
| Opus 5 | $0.00078 | $0.00725 |
| Sonnet 5 | $0.00031 | $0.00290 |
| Haiku 4.5 | $0.00016 | $0.00145 |
Grade A, and why
api-health-monitoring 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Monitoring Skill
Design complete observability stacks for any API: health checks, metrics, alerting, and dashboards.
Health Check Endpoints
Liveness check — is the process alive?
GET /health/live
Response 200: { "status": "ok" }
Response 503: { "status": "error", "reason": "OOM" }
Readiness check — can it serve traffic?
GET /health/ready
Response 200:
{
"status": "ready",
"checks": {
"database": "ok",
"cache": "ok",
"message_queue": "ok",
"external_api": "degraded"
}
}
Response 503: { "status": "not_ready", "checks": { "database": "error" } }
Deep health — full dependency tree
GET /health/deep
Response 200:
{
"status": "healthy",
"version": "2.1.0",
"uptime_seconds": 86400,
"dependencies": {
"postgres": { "status": "ok", "latency_ms": 2 },
"redis": { "status": "ok", "latency_ms": 0.5 },
"stripe": { "status": "ok", "latency_ms": 120 }
}
}
SLI / SLO / SLA Definitions
| Metric | SLI (what to measure) | SLO (target) | SLA (committed) |
|---|---|---|---|
| Availability | % of successful requests | 99.95% | 99.9% |
| Latency | p99 response time | < 500ms | < 1000ms |
| Error rate | % 5xx responses | < 0.1% | < 0.5% |
| Throughput | requests per second | > 1000 rps | > 500 rps |
Prometheus Metrics to Expose
GET /metrics (prometheus scrape endpoint)
# Request counters
http_requests_total{method, route, status_code}
http_request_duration_seconds{method, route} (histogram)
# Business metrics
api_active_users_total
api_db_query_duration_seconds{query_type}
api_cache_hit_ratio
api_queue_depth{queue_name}
# Error metrics
api_errors_total{error_type, route}
api_circuit_breaker_state{service}
Alerting Rules
# Critical — page immediately
- alert: HighErrorRate
expr: rate(http_requests_total{status_code=~"5.."}[5m]) / rate(http_requests_total[5m]) > 0.01
for: 2m
labels: { severity: critical }
annotations: { summary: "Error rate > 1%" }
- alert: APIDown
expr: up{job="api"} == 0
for: 1m
labels: { severity: critical }
- alert: HighLatency
expr: histogram_quantile(0.99, rate(http_request_duration_seconds_bucket[5m])) > 1.0
for: 5m
labels: { severity: warning }
# Warning — Slack notification
- alert: DatabaseSlow
expr: api_db_query_duration_seconds{quantile="0.95"} > 0.5
for: 10m
labels: { severity: warning }
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 · 202 lines · 156 tokens per session scan A 9f2745ad2c96
api-health-monitoring is a skill published in the GitHub repository LambdaTest/agent-skills (367 stars, last pushed today), licensed MIT. It adds 156 tokens to every session and 1,450 once invoked, about $0.0008 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
detecting-broken-object-property-level-authorization
Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
api-testing
API testing patterns for Playwright -- apiRequest fixture usage, Zod response schema creation and validation, test.step wrapping for multi-call tests, per-field negative/validation testing, path parameter fuzzing, and helper fixtures for shared setup/teardown. Use when writing or updating API test specs, adding tests…
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
pr-reviewer
Reviews a Git branch as a pull request against the base branch (auto-resolved from origin/HEAD — usually main or master) using this repo's own rules — the CLAUDE.md constitution and the .claude/skills/ that apply to the changed files. Fetches the branch, switches to it, diffs it against the merge-base, routes the…
test-standards
Spec file conventions for the Playwright scaffold — imports from test-options.ts, test file structure (describe / beforeEach / test / test.step), single-tag rule, functional vs E2E vs API vs setup test types, data-driven test loops against TS static data, web-first assertions, destructive-test cleanup, and test…