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 pyats-f5-ltmgit 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/pyats-f5-ltm)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/pyats-f5-ltm"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/pyats-f5-ltm/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/pyats-f5-ltm"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/pyats-f5-ltm.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.00075 | $0.05995 |
| Opus 5 | $0.00037 | $0.02998 |
| Sonnet 5 | $0.00015 | $0.01199 |
| Haiku 4.5 | $0.00007 | $0.00600 |
Grade A, and why
pyats-f5-ltm 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
F5 BIG-IP LTM/GTM Operations via pyATS
Testbed Requirements
F5 BIG-IP devices in the pyATS testbed:
devices:
bigip-01:
os: bigip
type: load-balancer
connections:
rest:
class: rest
ip: 10.0.0.20
port: 443
protocol: https
credentials:
default:
username: "%ENV{F5_USERNAME}"
password: "%ENV{F5_PASSWORD}"
How to Call
Use pyats_run_show_command with iControl REST API paths:
PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"bigip-01","command":"show ltm virtual"}'
Or for direct REST endpoints, the pyATS F5 connection maps these to iControl REST GETs.
LTM Endpoints
Virtual Servers
| Endpoint | Description |
|---|---|
/mgmt/tm/ltm/virtual |
All virtual servers — name, destination, pool, profiles, status |
/mgmt/tm/ltm/virtual-address |
Virtual server IP addresses and availability |
/mgmt/tm/ltm/traffic-matching-criteria |
Traffic matching rules for virtual servers |
/mgmt/tm/ltm/traffic-class |
Traffic classification rules |
Pools & Nodes
| Endpoint | Description |
|---|---|
/mgmt/tm/ltm/pool |
All pools — name, members, monitor, load balancing method |
/mgmt/tm/ltm/node |
All nodes — address, state (enabled/disabled), monitor status |
/mgmt/tm/ltm/default-node-monitor |
Default monitor for nodes |
Monitors
| Endpoint | Description |
|---|---|
/mgmt/tm/ltm/monitor/http |
HTTP health monitors |
/mgmt/tm/ltm/monitor/https |
HTTPS health monitors |
/mgmt/tm/ltm/monitor/tcp |
TCP health monitors |
/mgmt/tm/ltm/monitor/tcp-half-open |
TCP half-open monitors |
/mgmt/tm/ltm/monitor/tcp-echo |
TCP echo monitors |
/mgmt/tm/ltm/monitor/udp |
UDP health monitors |
/mgmt/tm/ltm/monitor/icmp |
ICMP (ping) monitors |
/mgmt/tm/ltm/monitor/gateway-icmp |
Gateway ICMP monitors |
/mgmt/tm/ltm/monitor/dns |
DNS monitors |
/mgmt/tm/ltm/monitor/ftp |
FTP monitors |
/mgmt/tm/ltm/monitor/sip |
SIP monitors |
/mgmt/tm/ltm/monitor/smtp |
SMTP monitors |
/mgmt/tm/ltm/monitor/pop3 |
POP3 monitors |
/mgmt/tm/ltm/monitor/imap |
IMAP monitors |
/mgmt/tm/ltm/monitor/ldap |
LDAP monitors |
/mgmt/tm/ltm/monitor/mysql |
MySQL monitors |
/mgmt/tm/ltm/monitor/mssql |
MSSQL monitors |
/mgmt/tm/ltm/monitor/oracle |
Oracle monitors |
/mgmt/tm/ltm/monitor/postgresql |
PostgreSQL monitors |
/mgmt/tm/ltm/monitor/radius |
RADIUS monitors |
/mgmt/tm/ltm/monitor/radius-accounting |
RADIUS accounting monitors |
/mgmt/tm/ltm/monitor/snmp-dca |
SNMP DCA monitors |
/mgmt/tm/ltm/monitor/snmp-dca-base |
SNMP DCA base monitors |
/mgmt/tm/ltm/monitor/external |
External (script-based) monitors |
/mgmt/tm/ltm/monitor/scripted |
Scripted monitors |
/mgmt/tm/ltm/monitor/inband |
Inband (passive) monitors |
/mgmt/tm/ltm/monitor/real-server |
Real server monitors |
/mgmt/tm/ltm/monitor/firepass |
FirePass monitors |
/mgmt/tm/ltm/monitor/wmi |
WMI monitors |
/mgmt/tm/ltm/monitor/wap |
WAP monitors |
/mgmt/tm/ltm/monitor/soap |
SOAP monitors |
/mgmt/tm/ltm/monitor/nntp |
NNTP monitors |
/mgmt/tm/ltm/monitor/smb |
SMB monitors |
/mgmt/tm/ltm/monitor/rpc |
RPC monitors |
/mgmt/tm/ltm/monitor/sasp |
SASP monitors |
/mgmt/tm/ltm/monitor/diameter |
Diameter monitors |
/mgmt/tm/ltm/monitor/mqtt |
MQTT monitors |
/mgmt/tm/ltm/monitor/module-score |
Module score monitors |
/mgmt/tm/ltm/monitor/virtual-location |
Virtual location monitors |
/mgmt/tm/ltm/monitor/none |
No monitor (placeholder) |
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 · 439 lines · 75 tokens per session scan A 854c5f48e1e8
pyats-f5-ltm is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 75 tokens to every session and 5,995 once invoked, about $0.0004 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…