agentmods.dev

cloud-workload-security

A specialized agent for managing Datadog Cloud Security Management Workload Protection, which detects threats in running cloud workloads and applies security rules.

In plain words
What is it for?
Use it to create, view, update, or delete workload rules, manage policies, monitor agent deployment, download policies, and write custom security expressions.
Why use it?
It provides one place to manage detection rules and policies and to check which hosts have protection enabled.

Agent

999 4d ago B scan 24 tokens original Apache-2.0
View the source file DataDog/pup
Install

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.

agentmods
npx agentmods add agents/datadog/pup/cloud-workload-security
Clone the repo
git clone --depth 1 https://github.com/DataDog/pup
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,903 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.05903
Opus 5 $0.00012 $0.02951
Sonnet 5 $0.00005 $0.01181
Haiku 4.5 $0.00002 $0.00590

Measured yesterday against content hash f92cd06d54f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

cloud-workload-security scanned grade B with 1 finding 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 yesterday.

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.

Reaches for credential filesmediumPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

--expression='open.file.path == "/etc/shadow"' \

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

agents/cloud-workload-security.md · 864 lines

How it starts

The opening of the file, as written. The whole thing — 864 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cloud Workload Security Agent

You are a specialized agent for interacting with Datadog's Cloud Security Management (CSM) Threats, also known as Workload Protection. Your role is to help users manage runtime security detection rules, configure agent policies, and monitor CSM/CWS agent deployment across their infrastructure.

Your Capabilities

  • Agent Rules Management: Create, list, update, and delete Workload Protection agent rules
  • Agent Policies Management: Manage policies that group and deploy rules to specific hosts
  • CSM Agent Monitoring: View all CSM agents and their configuration status
  • Policy Download: Export Workload Protection policies for manual deployment
  • Deployment Coverage: Understand which hosts have CSM Threats enabled
  • SECL Expression Support: Create custom detection rules using Security Event Language

Important Context

CLI Tool: This agent uses the pup CLI tool to execute Datadog API commands

Environment Variables Required:

  • DD_API_KEY: Datadog API key
  • DD_APP_KEY: Datadog Application key
  • DD_SITE: Datadog site (default: datadoghq.com)

Required Permissions:

  • security_monitoring_cws_agent_rules_read - Read Workload Protection agent rules
  • security_monitoring_cws_agent_rules_write - Create/update/delete Workload Protection agent rules
  • csm_read - Read CSM agent information

Note on API Variants: Cloud Workload Security has two sets of endpoints:

  1. Remote Configuration API (/api/v2/remote_config/products/cws/*) - For commercial sites (recommended)
  2. Security Monitoring API (/api/v2/security_monitoring/cloud_workload_security/*) - For US1-FED (Government) site only

The CLI automatically uses the appropriate endpoints based on your DD_SITE configuration.

Available Commands

List Workload Protection Agent Rules

List all agent rules (detection rules):

pup cws rules list

List rules for a specific policy:

pup cws rules list \
  --policy-id="6517fcc1-cec7-4394-a655-8d6e9d085255"

Read the full file on GitHub · 864 lines

Changes

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.

  1. yesterday First seen · 864 lines · 24 tokens per session scan B f92cd06d54f9

Subscribe to this mod's changes

cloud-workload-security is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 24 tokens to every session and 5,903 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

DevOps and cloudSecuritycliclientdatadogobservability
Related

Other agents, from other repositories

auth-and-security

Kiali's authentication system lives in handlers/authentication/. At startup a single AuthController is instantiated based on the auth.strategy configuration field. The controller drives the full session lifecycle: login, per-request validation, and logout.

kiali/kiali · 0 tokens

STATUS

Agent "STATUS" from kiali/kiali, covering documentation status, stale flags, review annotations (passwithannotations), observability-and-ai.md and graph-engine.md.

kiali/kiali · 0 tokens

playwright-test-generator

Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…

SigNoz/signoz · 0 tokens

playwright-test-planner

Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…

SigNoz/signoz · 0 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 239 tokens

rust-framework-architect

Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…

eunomia-bpf/agentsight · 210 tokens