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 eobarretooo/ClawLite --skill healthcheckgit clone --depth 1 https://github.com/eobarretooo/ClawLiteWrote 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/eobarretooo/clawlite/healthcheck)<a href="https://agentmods.dev/skills/eobarretooo/clawlite/healthcheck"><img src="https://agentmods.dev/badge/skills/eobarretooo/clawlite/healthcheck.svg" alt="Measured on agentmods" 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.00020 | $0.00310 |
| Opus 5 | $0.00010 | $0.00155 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
healthcheck 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 8d 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.
What it actually says
Healthcheck
Use this skill when the user asks for machine hardening, runtime health, readiness checks, or operational review.
Baseline checks (read-only)
clawlite statusclawlite validate configclawlite validate providerclawlite validate channelsclawlite validate preflight --gateway-url http://127.0.0.1:8787- Gateway probes:
GET /v1/statusandGET /v1/diagnostics
Prefer these checks before proposing any changes.
Host hardening guardrails
- Confirm how the user connects (local, SSH, VPN, remote desktop) before touching access controls.
- Require explicit approval before any state-changing action.
- Use staged, reversible changes with rollback notes.
- Never claim ClawLite changes OS firewall/SSH/update policy automatically; those are host-level tasks.
Cron safety
clawlite cron list/add/remove/enable/disable/run can schedule operational checks.
Only use cron commands after explicit user approval.
Output format
Return:
- Current posture (what is healthy / what is risky)
- Exact remediation plan (step-by-step)
- Verification plan (
status,validate, and endpoint re-checks)
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.
- 8d ago First seen · 43 lines · 20 tokens per session scan A 0f0fe4ac651a
healthcheck is a skill published in the GitHub repository eobarretooo/ClawLite (49 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 310 once invoked, about $0.0001 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
a0-create-agent
Create a new Agent Zero agent profile (subordinate). Covers where profiles live (user / plugin-distributed / project-scoped), the agent.yaml schema, the prompt inheritance & override model, and optional profile-specific tools and extensions. Use for any "create/add/new agent profile" request.
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
linux-desktop
Use only for Agent Zero's built-in Docker/Xpra Linux Desktop, XFCE apps, LibreOffice GUI apps, file manager, terminal, or visual workflows inside the Agent Zero runtime. Not for A0 CLI /computer-use or computeruseremote host control.
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
a0-review-plugin
Full audit of Agent Zero plugins in usr/plugins/. Reviews manifest validity, directory structure, code patterns (Store Gating, notifications, imports), security, and duplicate detection against the community index. Use when asked to review, audit, validate, or check an existing plugin before using or contributing it.
host-computer-use-linux
Backend-specific Linux guidance for computeruseremote. Load after status or startsession reports backendfamily linux, backendid wayland, or AT-SPI features. Covers AT-SPI structural targeting, Wayland portal caveats, and screenshot verification.