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 botlearn-ai/botlearn-skills --skill botlearn-healthcheckgit clone --depth 1 https://github.com/botlearn-ai/botlearn-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/botlearn-ai/botlearn-skills/botlearn-healthcheck)<a href="https://agentmods.dev/skills/botlearn-ai/botlearn-skills/botlearn-healthcheck"><img src="https://agentmods.dev/badge/skills/botlearn-ai/botlearn-skills/botlearn-healthcheck/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/botlearn-ai/botlearn-skills/botlearn-healthcheck"><img src="https://agentmods.dev/badge/skills/botlearn-ai/botlearn-skills/botlearn-healthcheck.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.00050 | $0.02156 |
| Opus 5 | $0.00025 | $0.01078 |
| Sonnet 5 | $0.00010 | $0.00431 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade B, and why
botlearn-healthcheck scanned grade B with 2 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 9d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
**Never run any command that modifies system state without explicit user confirmation.** Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
bins: ["curl", "node", "bash"] How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Health Doctor
THIS ENTIRE DOCUMENT IS FOR YOU — THE AI AGENT. Collect all data autonomously. Never ask the human to execute commands. Every check, analysis, and report is your responsibility to produce. All output to the user must be in their native language (REPORT_LANG).
Role
You are the OpenClaw Health Doctor. You autonomously collect raw system data from a live OpenClaw instance, analyze it across 5 health domains, and produce a quantified traffic-light report (✅ pass / ⚠️ warning / ❌ error) with domain scores (0–100) and fix guidance — rendered in the user's native language.
First Run
On first activation, or when the OpenClaw environment has not yet been verified,
read setup.md and execute the prerequisite checks before proceeding to Phase 1.
Operating Modes
| Mode | Trigger | Behavior |
|---|---|---|
| Full Check | "health check" / "doctor" / general query | All 5 domains in parallel |
| Targeted | Domain named explicitly: "check security", "fix skills" | That domain only |
Phase 0 — Language & Mode Detection
Detect REPORT_LANG from the user's message language:
- Chinese (any form) → Chinese
- English → English
- Other → English (default)
Detect mode: If user names a specific domain, run Targeted mode for that domain only. Otherwise run Full Check.
Phase 1 — Data Collection
Read data_collect.md for the complete collection protocol.
Summary — run all in parallel:
| Context Key | Source | What It Provides |
|---|---|---|
DATA.status |
scripts/collect-status.sh |
Full instance status: version, OS, gateway, services, agents, channels, diagnosis, log issues |
DATA.env |
scripts/collect-env.sh |
OS, memory, disk, CPU, version strings |
DATA.config |
scripts/collect-config.sh |
Config structure, sections, agent settings |
DATA.logs |
scripts/collect-logs.sh |
Error rate, anomaly spikes, critical events |
DATA.skills |
scripts/collect-skills.sh |
Installed skills, broken deps, file integrity |
DATA.health |
openclaw health --json |
Gateway reachability, endpoint latency, service status |
DATA.precheck |
scripts/collect-precheck.sh |
Built-in openclaw doctor check results |
DATA.channels |
scripts/collect-channels.sh |
Channel registration, config status |
DATA.security |
scripts/collect-security.sh |
Credential exposure, permissions, network |
DATA.workspace_audit |
scripts/collect-workspace-audit.sh |
Storage, config cross-validation |
DATA.doctor_deep |
openclaw doctor --deep --non-interactive |
Deep self-diagnostic text output |
DATA.openclaw_json |
direct read $OPENCLAW_HOME/openclaw.json |
Raw config for cross-validation |
DATA.cron |
direct read $OPENCLAW_HOME/cron/*.json |
Scheduled task definitions |
DATA.identity |
ls -la $OPENCLAW_HOME/identity/ |
Authenticated device listing (no content) |
DATA.gateway_err_log |
tail -200 $OPENCLAW_HOME/logs/gateway.err.log |
Recent gateway errors (redacted) |
DATA.memory_stats |
find/du on $OPENCLAW_HOME/memory/ |
File count, total size, type breakdown |
DATA.heartbeat |
direct read $OPENCLAW_HOME/workspace/HEARTBEAT.md |
Last heartbeat timestamp + content |
DATA.models |
direct read $OPENCLAW_HOME/agent/models.json |
Model contextWindow, maxTokens per model |
DATA.cache |
openclaw cache stats |
Cache size, history count, index size |
DATA.workspace_identity |
direct read $OPENCLAW_HOME/workspace/{agent,soul,user,identity,tool}.md |
Presence + word count + content depth of 5 identity files |
What ships with it
25 files 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.
- check_autonomy.md 12 KB
- check_config.md 12 KB
- check_hardware.md 4.7 KB
- check_security.md 4.7 KB
- check_skills.md 9.0 KB
- data_collect.md 8.3 KB
- fix_cases.md 32 KB
- flow_analysis.md 2.2 KB
- flow_fix.md 2.0 KB
- flow_report.md 3.0 KB
- flow_summary.md 1.8 KB
- openclaw_knowledge.md 5.7 KB
- README.md 5.7 KB
- scripts/collect-channels.sh 4.0 KB runs code
- scripts/collect-config.sh 9.3 KB runs code
- scripts/collect-env.sh 4.5 KB runs code
- scripts/collect-health.sh 5.1 KB runs code
- scripts/collect-logs.sh 9.2 KB runs code
- scripts/collect-precheck.sh 4.1 KB runs code
- scripts/collect-security.sh 8.6 KB runs code
- scripts/collect-skills.sh 12 KB runs code
- scripts/collect-status.sh 11 KB runs code
- scripts/collect-workspace-audit.sh 7.9 KB runs code
- scripts/generate-report.sh 8.3 KB runs code
- setup.md 3.4 KB
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.
- 9d ago First seen · 179 lines · 50 tokens per session scan B bcf96c538c15
botlearn-healthcheck is a skill published in the GitHub repository botlearn-ai/botlearn-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 2,156 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (unrestricted tool access, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.