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 hamzaPixl/pixl-ai --skill runbookgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/runbook)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/runbook"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/runbook/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/hamzapixl/pixl-ai/runbook"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/runbook.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.00045 | $0.00974 |
| Opus 5.5 | $0.00018 | $0.00390 |
| Sonnet 5.5 | $0.00009 | $0.00195 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
runbook 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 1mo 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.
- **Health check**: `curl <url>/health` How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Two modes:
- Investigate: Live incident response — follow the triage ladder to isolate root cause fast
- Document: Generate a runbook for a service so the next incident takes minutes, not hours
Mode Detection
/runbook payments → investigate live incident in payments service
/runbook payments --postmortem → document lessons after the incident
/runbook api → triage an API degradation
Investigate Mode
Phase 1: Triage (first 5 minutes)
Goal: Determine blast radius and whether to escalate immediately.
- What is failing? (service, endpoint, feature, region, all users vs subset)
- When did it start? (
git log --since, deploy timestamps, monitoring alerts) - What changed? (recent deploys, config changes, dependency updates)
- What is the user impact? (errors returned, data corruption, performance degradation)
Escalate immediately if: data loss possible, payment processing affected, auth broken for all users.
Phase 2: Diagnose (5–20 minutes)
Goal: Narrow to a single root cause hypothesis.
Check in order:
- Application logs — look for error spikes, stack traces, new error codes
- Infrastructure — CPU, memory, disk, connection pools, queue depths
- Dependencies — database latency, external API errors, cache hit rates
- Recent changes — diff between last good deploy and current
Useful commands:
# Application logs (last 100 errors)
grep -i "error\|exception\|fatal" app.log | tail -100
# Process health
ps aux | grep <service>
# or: systemctl status <service>
# Port/connection check
lsof -i :<port>
netstat -an | grep <port>
# Disk space
df -h
du -sh /* | sort -rh | head -10
Phase 3: Remediate
Goal: Restore service — accept temporary degradation over outage.
Remediation ladder (try in order):
- Rollback — fastest if a recent deploy caused it:
git revert HEADor redeploy previous image - Restart — clears memory leaks, zombie processes:
systemctl restart <service>orpm2 restart all - Scale — if load-caused: increase replicas/instances
- Circuit break — disable the failing feature/dependency to restore partial service
- Hotfix — only if rollback is not possible and root cause is confirmed
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.
- 1mo ago First seen · 122 lines · 45 tokens per session scan A 400e605c40b6
runbook is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 974 once invoked, about $0.0002 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.