OpenClaw Agent Skills is a shared repository of reusable workflows for coding agents working on OpenClaw projects. It provides skills for activities such as code-review closeout, behavior validation, session handoff, remote testing, transcript provenance, and viewing agent sessions. The catalogue entries are the project’s distributed skills and instruction.
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 openclaw/agent-skills --skill behavior-validatorgit clone --depth 1 https://github.com/openclaw/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/openclaw/agent-skills/behavior-validator)<a href="https://agentmods.dev/skills/openclaw/agent-skills/behavior-validator"><img src="https://agentmods.dev/badge/skills/openclaw/agent-skills/behavior-validator/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/openclaw/agent-skills/behavior-validator"><img src="https://agentmods.dev/badge/skills/openclaw/agent-skills/behavior-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 25 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00026 | $0.00743 |
| Opus 5.5 | $0.00010 | $0.00297 |
| Sonnet 5.5 | $0.00005 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade B, and why
behavior-validator scanned grade B 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 700 "$validator_dir" Copies of this mod
1 near-identical copy found in the catalogue:
- behavior-validator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavior Validator
Validate observable behavior without inspecting source. Use this as the black-box companion to code-aware review: autoreview judges the change bundle, while behavior-validator judges the running product, CLI, API, or generated artifact against a behavior contract.
Contract
- Read the behavior contract first. If none exists, write a short one from the user request before testing. See
references/contract-template.md. - Stay source-blind. Do not inspect source files, diffs, tests, git history, implementation notes, build internals, or review bundles.
- Interact only through user-visible or operator-visible surfaces: browser, CLI, API, generated files, public logs, screenshots, accessibility trees, or documented runtime output.
- Treat implementation-looking evidence as contamination. If source access is required to continue, stop and report
blocked_source_required. - Report findings against contract clauses and observable steps, not code locations.
- Do not mark a workflow as passing until each relevant contract clause is pass, fail, blocked, or out of scope.
Isolation
Prefer a source-blind workspace:
validator_dir="$(mktemp -d "${TMPDIR:-/tmp}/behavior-validator-run.XXXXXX")"
chmod 700 "$validator_dir"
cp behavior-contract.md "$validator_dir/"
cd "$validator_dir"
Launch or connect to the target from the contract. Keep only the contract, allowed fixtures, and redacted captured evidence in the private validator workspace. Supply credentials through approved secret tooling or exact environment variables; never copy credential values into the workspace, report, screenshots, or logs. Do not use fixed shared paths for contracts or captured evidence. If the app must be started from the source checkout, start it from a separate terminal and do not read source while validating.
Workflow
- Parse the contract into user tasks, expected behavior, anti-cheat probes, setup, and evidence requirements.
- Prepare runtime access: target URL, CLI command, API endpoint, fixture data, credentials, or generated artifact path.
- Exercise each user task as a real user or operator would.
- Run anti-cheat probes: vary fixture data, refresh/retry, test empty and invalid inputs, verify persistence, inspect generated output, and confirm buttons/commands perform real work rather than only displaying success text.
- Capture evidence as compact redacted notes, screenshots, terminal excerpts, response summaries, file summaries, or accessibility observations. Omit credentials, tokens, cookies, private user data, and unrelated log content.
- Emit a structured report. Use
references/report-schema.mdwhen a machine-readable report is useful. - If the orchestrator fixes a finding, rerun only the affected contract clauses plus any nearby regression probes.
What ships with it
3 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.
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 · 59 lines · 26 tokens per session scan B 481904b1ffe6
behavior-validator is a skill published in the GitHub repository openclaw/agent-skills (1,106 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 743 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.