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 claroty-risk-triagegit 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/claroty-risk-triage)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/claroty-risk-triage"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/claroty-risk-triage/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/claroty-risk-triage"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/claroty-risk-triage.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.01547 |
| Opus 5 | $0.00025 | $0.00773 |
| Sonnet 5 | $0.00010 | $0.00309 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
claroty-risk-triage 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 13d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claroty Risk Triage
Unified alert + vulnerability triage for OT / IoT / IoMT environments via Claroty xDome. Alerts and vulnerabilities are bundled into one skill because real incident response crosses the boundary constantly — operators investigate an alert, pivot to the affected device's CVE list, and back to the alert label.
When to Use
- Triaging Claroty xDome alerts by severity, site, or assignee
- Computing the blast radius of an alert (which devices, which protocols)
- Inspecting vulnerability findings, filtering by CVSS, and listing affected devices
- Marking a CVE as not-relevant for a specific device (mitigation in place, compensating control, patched out-of-band)
- Acknowledging, labelling, or assigning alerts during a hunt
- Handing off to
ise-incident-responsefor endpoint quarantine or toservicenow-change-workflowfor a remediation CR
MCP Server
- Server:
claroty-mcp - Command:
python3 -u mcp-servers/claroty-mcp/claroty_mcp_server.py(stdio transport) - Auth: Bearer token via
CLAROTY_API_TOKEN - ITSM: Write operations require a
CHG\d+CR; bypassed inNETCLAW_LAB_MODE=true
Available Tools
| Tool | Parameters | What It Does |
|---|---|---|
list_alerts |
severity?, status?, site_id?, assignee?, limit?, offset?, max_items? |
List security alerts with filters |
get_alert_with_devices |
alert_id, device_limit? |
Alert + affected devices in one call |
list_vulnerabilities |
severity?, cvss_min?, cve_contains?, limit?, offset?, max_items? |
List CVE-aligned findings |
get_vulnerable_devices |
vulnerability_id, limit?, offset? |
Devices affected by one CVE (blast radius) |
acknowledge_alert |
alert_id, resolution, cr_number, note? |
Write (ITSM-gated) — set resolution state |
set_vulnerability_relevance |
device_id, vulnerability_id, relevant, cr_number, note? |
Write (ITSM-gated) — suppress / re-enable CVE on a device |
label_alerts |
alert_ids, labels, cr_number, replace? |
Write (ITSM-gated) — apply / replace labels |
assign_alerts |
alert_ids, assignee, cr_number, note? |
Write (ITSM-gated) — assign alerts to a user / queue |
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.
- 13d ago First seen · 117 lines · 50 tokens per session scan A f35e78aed9ce
claroty-risk-triage 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,547 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…