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 deepelementlab/saddle --skill openclaw-plugingit clone --depth 1 https://github.com/deepelementlab/saddleWrote 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/deepelementlab/saddle/openclaw-plugin)<a href="https://agentmods.dev/skills/deepelementlab/saddle/openclaw-plugin"><img src="https://agentmods.dev/badge/skills/deepelementlab/saddle/openclaw-plugin/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/deepelementlab/saddle/openclaw-plugin"><img src="https://agentmods.dev/badge/skills/deepelementlab/saddle/openclaw-plugin.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.00000 | $0.00433 |
| Opus 5.5 | $0.00000 | $0.00173 |
| Sonnet 5.5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
openclaw-plugin 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 2mo 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
[
"tests/test_memory_api.py::test_health",
"tests/test_memory_api.py::test_memory_group_search",
"tests/test_mode_cli.py::test_cli_mode_list",
"tests/test_mode_cli.py::test_cli_mode_show",
"tests/test_mode_cli.py::test_cli_mode_validate_fail",
"tests/test_mode_cli.py::test_cli_mode_validate_ok",
"tests/test_mode_cli.py::test_cli_root_help_uses_prog_name_saddle",
"tests/test_mode_cli.py::test_list_mode_names_pkg_root",
"tests/test_mode_cli.py::test_python_m_saddle_help",
"tests/test_mode_cli.py::test_python_m_saddle_no_args_shows_help_exit_zero",
"tests/test_mode_cli.py::test_validate_default_mode_ok",
"tests/test_mode_cli.py::test_validate_invalid_pipeline_stage",
"tests/test_modes_api.py::test_modes_list_and_show",
"tests/test_modes_api.py::test_modes_validate_and_save",
"tests/test_modes_loader.py::test_default_mode_values",
"tests/test_modes_loader.py::test_load_mode_from_yaml",
"tests/test_modes_resolver.py::test_cli_overrides_take_precedence",
"tests/test_pipeline_api.py::test_pipeline_run_bad_project_root",
"tests/test_pipeline_api.py::test_pipeline_run_ok_mocked",
"tests/test_pipeline_api.py::test_pipeline_run_validation",
"tests/test_pipeline_runner.py::test_pipeline_default_order",
"tests/test_pipeline_runner.py::test_pipeline_respects_disabled_stage",
"tests/test_plugin_hooks.py::test_claude_inject_memories_hook",
"tests/test_plugin_hooks.py::test_claude_store_memories_hook",
"tests/test_plugin_http_contract.py::test_health",
"tests/test_plugin_http_contract.py::test_post_memories_group_payload",
"tests/test_plugin_http_contract.py::test_post_search_matches_plugin_body",
"tests/test_spec_store.py::test_spec_store_roundtrip",
"tests/test_studio_static.py::test_build_studio_router_serves_spa_and_What ships with it
17 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.
- bin/install.js 9.6 KB runs code
- bin/run-once.js 1.2 KB runs code
- examples/openclaw.sample.json 596 B
- index.js 610 B runs code
- openclaw.plugin.json 1.4 KB
- package.json 824 B
- README.md 3.1 KB
- src/api.js 1.6 KB runs code
- src/config.js 425 B runs code
- src/convert.js 1.8 KB runs code
- src/engine.js 6.1 KB runs code
- src/http.js 1.7 KB runs code
- src/messages.js 2.2 KB runs code
- src/prompt.js 3.0 KB runs code
- src/subagent-assembler.js 1.3 KB runs code
- src/types.js 364 B runs code
- test/api.test.js 2.3 KB runs code
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.
- 2mo ago First seen · 30 lines · 0 tokens per session scan A e7bd17a42291
openclaw-plugin is a skill published in the GitHub repository deepelementlab/saddle (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 433 tokens. 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-31.
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.
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.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.