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 nso-service-mgmtgit 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/nso-service-mgmt)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/nso-service-mgmt"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/nso-service-mgmt/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/nso-service-mgmt"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/nso-service-mgmt.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.00050 | $0.01550 |
| Opus 5 | $0.00025 | $0.00775 |
| Sonnet 5 | $0.00010 | $0.00310 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
nso-service-mgmt 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 9d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NSO Service Management
MCP Server
- Command:
cisco-nso-mcp-server(pip-installed, stdio transport) - Requires:
NSO_ADDRESS,NSO_USERNAME,NSO_PASSWORDenvironment variables
Available Tools
| Tool | Parameters | What It Does |
|---|---|---|
get_service_types |
none | List all available service types in NSO (L3VPN, VPLS, ACL, etc.) |
get_services |
service_type |
List all service instances for a given service type |
What Are NSO Services?
NSO services are the core value of NSO. Instead of configuring devices one at a time, you define a service (e.g., "L3VPN between Site-A and Site-B") and NSO:
- Translates the service intent into per-device CLI/NETCONF configuration
- Deploys the config to all affected devices transactionally
- Tracks what config belongs to which service (service meta-data)
- Enables rollback — delete the service and all its config is cleanly removed
Common service types include:
- L3VPN — Layer 3 VPN provisioning across PE routers
- L2VPN / VPLS — Layer 2 VPN / VPLS services
- ACL Management — Centralized ACL provisioning
- QoS Policies — Quality of service templates across devices
- Interface Provisioning — Standardized interface configurations
- Firewall Rules — Security policy deployment
- Custom Services — Any service package developed for your environment
Workflow: Service Discovery
When a user asks "what services does NSO have?" or "what can NSO provision?":
- Get service types:
get_service_typesto list all available service packages - For each type:
get_servicesto list deployed instances - Report: Table of service types, instance counts, and deployment status
Workflow: Service Inventory Report
When a user needs to understand what's deployed:
- List service types:
get_service_types - For each interesting type:
get_serviceswith the service type name - Cross-reference with devices: Use
get_device_config(nso-device-ops) to see the config NSO deployed - Report: Service name, type, affected devices, deployment status
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.
- 9d ago First seen · 130 lines · 50 tokens per session scan A b1e49f5e0641
nso-service-mgmt is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,550 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-09-03.
Other skills, from other repositories
ha-integration-solution
Plans and orchestrates a complete Home Assistant Python custom-integration backend from a result-oriented device/cloud/API requirement, driven by a chosen quality-scale target tier (Bronze–Platinum), so the user never picks individual skills. Decomposes the requirement into a minimal dependency-ordered plan for the…
ha-esphome-solution
Plans and orchestrates a complete ESPHome device or fleet result from a requirement, so the user never has to pick which ESPHome skill produces what. Decomposes it into the minimal dependency-ordered set of artifacts across the ha-esphome- family — repository layout and packages, the device file, sensors and buses…
ha-automation-solution
Plans and orchestrates a complete Home Assistant YAML solution from a result-oriented requirement, so the user never has to pick which authoring skill to use. Decomposes the requirement into the minimal combination of artifacts across the ha-automation skill family, presents a dependency-ordered artifact plan for…
surge-manager
A skill for managing Surge configurations and Tailscale devices. Surge is a network proxy and traffic-routing app, while Tailscale connects devices through a private network.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
trigger-authoring-chat-agent
Author and run a durable AI chat agent with chat.agent from @trigger.dev/sdk/ai: the per-turn run loop, why you MUST take streamText from the run argument rather than importing it from ai, returning a StreamTextResult vs calling chat.pipe(), the two server actions (chat.createStartSessionAction +…