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 automateyournetwork/netclaw --skill cml-lab-lifecyclegit 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-lab-lifecycle)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/cml-lab-lifecycle"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/cml-lab-lifecycle.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01703 |
| Opus 5 | $0.00028 | $0.00851 |
| Sonnet 5 | $0.00011 | $0.00341 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
cml-lab-lifecycle 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CML Lab Lifecycle Management
MCP Server
- Command:
cml-mcp(pip-installed, stdio transport) - Requires:
CML_URL,CML_USERNAME,CML_PASSWORDenvironment variables - Optional:
CML_VERIFY_SSL(default: true)
Available Tools
Lab CRUD Operations
| Tool | Parameters | What It Does |
|---|---|---|
create_lab |
title |
Create a new empty lab with a title |
get_lab |
lab_id or lab_title |
Get lab details (state, node count, link count) |
get_labs |
none | List all labs on the CML server |
start_lab |
lab_id or lab_title |
Start all nodes in a lab (boot the topology) |
stop_lab |
lab_id or lab_title |
Stop all nodes in a lab (graceful shutdown) |
wipe_lab |
lab_id or lab_title |
Wipe lab node configurations (reset to factory) |
delete_lab |
lab_id or lab_title |
Delete a lab permanently |
Lab Import/Export
| Tool | Parameters | What It Does |
|---|---|---|
import_lab |
topology (YAML string) |
Import a lab from CML topology YAML |
export_lab |
lab_id or lab_title |
Export a lab as CML topology YAML |
clone_lab |
lab_id or lab_title |
Clone an existing lab (deep copy) |
download_lab_configs |
lab_id or lab_title |
Download all node configs from a running lab |
Workflow: Create a Lab from Scratch (Slack)
When a user says something like "build me a 3-router OSPF lab" in Slack:
- Create the lab: Use
create_labwith a descriptive title - Add nodes: (See cml-topology-builder skill) Add routers, switches, servers
- Wire the topology: (See cml-topology-builder skill) Create interfaces and links
- Apply configs: (See cml-node-operations skill) Set startup configs
- Start the lab: Use
start_labto boot everything - Verify convergence: (See cml-node-operations skill) Execute show commands to verify routing
- Report back: Tell the user the lab is ready with node names and management IPs
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 · 163 lines · 55 tokens per session scan A 6fd75b11184c
cml-lab-lifecycle is a skill published in the GitHub repository automateyournetwork/netclaw (650 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 1,703 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
background
Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage .hyperflow/background/registry.json and the per-agent output buffers at .hyperflow/background/ .md. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents"…
flush
Use when the user wants to manually flush a deferred-commit queue from a prior or interrupted chain. Reads .hyperflow/commits-queue/manifest.json, fast-forwards the staging branch onto the user's branch, deletes staging, clears the queue. Recovery interface when a chain crashed before its Step 4 auto-flush ran.…
evaluating-cosmos-policy
Evaluates NVIDIA Cosmos Policy on LIBERO and RoboCasa simulation environments. Use when setting up cosmos-policy for robot manipulation evaluation, running headless GPU evaluations with EGL rendering, or profiling inference latency on cluster or local GPU machines.
lingtai-tui-help
Anything you need to know about LingTai TUI. Read this first for the stable mental model, feature map, interface/slash-command help, or the right source/manual route for a TUI question. Exact command prose lives in the localized help assets, Go structure lives in lingtai-tui-anatomy, and presets, Portal, tutorials…
cocotrace
Build and query the SHA-256 requirements-to-implementation traceability graph across lifecycle artifacts.
mission-orchestrator
Orchestrates full project lifecycle by auto-detecting state and routing to the correct phase. Use when starting or resuming a project mid-workflow.