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 clab-lab-managementgit 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/clab-lab-management)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/clab-lab-management"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/clab-lab-management/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/automateyournetwork/netclaw/clab-lab-management"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/clab-lab-management.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.01880 |
| Opus 5 | $0.00034 | $0.00940 |
| Sonnet 5 | $0.00013 | $0.00376 |
| Haiku 4.5 | $0.00007 | $0.00188 |
Grade A, and why
clab-lab-management 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 10d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ContainerLab Lab Management
MCP Server
- Command:
python3 -u $CLAB_MCP_SCRIPT(stdio transport) - Requires:
CLAB_API_SERVER_URL,CLAB_API_USERNAME,CLAB_API_PASSWORDenvironment variables - Auto-authentication: Every tool call auto-authenticates — no explicit
authenticatecall needed
How to Call Tools
python3 $MCP_CALL "python3 -u $CLAB_MCP_SCRIPT" <tool_name> '<args_json>'
Available Tools
| Tool | Parameters | What It Does |
|---|---|---|
authenticate |
apiServerURL, username, password |
Manual auth override (optional — auto-auth handles normal usage) |
listLabs |
none | List all labs on the ContainerLab server |
deployLab |
topologyContent (JSON object), reconfigure (bool) |
Deploy a new lab topology |
inspectLab |
labName, details (bool) |
Get lab details, node status, management IPs |
execCommand |
labName, command, nodeName (optional) |
Execute a command on one or all nodes |
destroyLab |
labName, cleanup (bool), graceful (bool) |
Destroy a lab and clean up resources |
Workflow: Deploy a New Lab
When a user wants to create a containerized network lab:
- List existing labs:
listLabs— check what's already running, avoid name conflicts - Deploy topology:
deployLabwith a topology JSON object - Inspect lab:
inspectLabwithdetails: true— verify success, get management IPs - Execute commands:
execCommand— run show commands to verify connectivity - Report back: Tell the user the lab is ready with node names and management IPs
Example: 2-Node SR Linux Lab
# List existing labs
python3 $MCP_CALL "python3 -u $CLAB_MCP_SCRIPT" listLabs '{}'
# Deploy
python3 $MCP_CALL "python3 -u $CLAB_MCP_SCRIPT" deployLab '{"topologyContent":{"name":"srlinux-demo","topology":{"nodes":{"srl1":{"kind":"nokia_srlinux","image":"ghcr.io/nokia/srlinux:latest","type":"ixrd2l"},"srl2":{"kind":"nokia_srlinux","image":"ghcr.io/nokia/srlinux:latest","type":"ixrd2l"}},"links":[{"endpoints":["srl1:e1-1","srl2:e1-1"]},{"endpoints":["srl1:e1-2","srl2:e1-2"]}]}}}'
# Inspect
python3 $MCP_CALL "python3 -u $CLAB_MCP_SCRIPT" inspectLab '{"labName":"srlinux-demo","details":true}'
# Execute command
python3 $MCP_CALL "python3 -u $CLAB_MCP_SCRIPT" execCommand '{"labName":"srlinux-demo","nodeName":"srl1","command":"show version"}'
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.
- 10d ago First seen · 164 lines · 67 tokens per session scan A 3957e64b240a
clab-lab-management is a skill published in the GitHub repository automateyournetwork/netclaw (652 stars, last pushed 3d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,880 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.