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 agentmods add skills/automateyournetwork/netclaw/cml-node-operationsnpx skills add automateyournetwork/netclaw --skill cml-node-operationsgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/cml-node-operations)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/cml-node-operations"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/cml-node-operations.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.00054 | $0.02176 |
| Opus 5 | $0.00027 | $0.01088 |
| Sonnet 5 | $0.00011 | $0.00435 |
| Haiku 4.5 | $0.00005 | $0.00218 |
Grade A, and why
cml-node-operations 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CML Node Operations
MCP Server
- Command:
cml-mcp(pip-installed, stdio transport) - Requires:
CML_URL,CML_USERNAME,CML_PASSWORDenvironment variables - Optional:
cml-mcp[pyats]for CLI execution via pyATS
Available Tools
Node Lifecycle
| Tool | Parameters | What It Does |
|---|---|---|
start_node |
lab_id/lab_title, node_id/node_label |
Start (boot) a single node |
stop_node |
lab_id/lab_title, node_id/node_label |
Stop (shutdown) a single node |
get_node |
lab_id/lab_title, node_id/node_label |
Get node details: state, CPU, RAM, interfaces, config |
get_nodes |
lab_id/lab_title |
List all nodes with their current states |
wipe_node |
lab_id/lab_title, node_id/node_label |
Wipe a node's configuration (reset to default) |
Configuration Management
| Tool | Parameters | What It Does |
|---|---|---|
set_node_config |
lab_id/lab_title, node_id/node_label, config |
Set a node's startup configuration |
get_node_config |
lab_id/lab_title, node_id/node_label |
Get a node's current configuration |
download_lab_configs |
lab_id/lab_title |
Download all node configs from a running lab |
Console & CLI Access
| Tool | Parameters | What It Does |
|---|---|---|
get_node_console |
lab_id/lab_title, node_id/node_label |
Get console connection details (URL, protocol) |
get_node_console_log |
lab_id/lab_title, node_id/node_label, lines? |
Retrieve console log output from a running node |
execute_command |
lab_id/lab_title, node_id/node_label, command |
Execute a CLI command on a running node (requires pyATS) |
Node States
| State | Meaning |
|---|---|
DEFINED_ON_CORE |
Node exists but is not running |
BOOTING |
Node is in the process of booting |
BOOTED |
Node has finished booting and is reachable |
STOPPED |
Node has been shut down |
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.
- 6d ago First seen · 252 lines · 54 tokens per session scan A 5781d543c2ee
cml-node-operations is a skill published in the GitHub repository automateyournetwork/netclaw (650 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 2,176 once invoked, about $0.0003 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
write-documentation
Write and format Rust documentation correctly. Apply proactively when writing code with rustdoc comments (//! or ///). Covers voice & tone, prose style (opening lines, explicit subjects, verb tense), structure (inverted pyramid), intra-doc links (crate:: paths, reference-style), constant conventions (binary/byte…
organize-modules
Apply private modules with public re-exports (barrel export) pattern for clean API design. Includes conditional visibility for docs and tests. Use when creating modules, organizing mod.rs files, or before creating commits.
check-bounds-safety
Apply type-safe bounds checking patterns using VPIndex/VPLength types instead of usize. Use when working with arrays, buffers, cursors, viewports, or any code that handles indices and lengths.
check-code-quality
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
analyze-performance
Establish performance baselines and detect regressions using flamegraph analysis. Use when optimizing performance-critical code, investigating performance issues, or before creating commits with performance-sensitive changes.
run-clippy
Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.