static-analysis

A Datadog code-security tool for static analysis and dependency analysis. Static analysis checks source code without running it, while dependency analysis checks libraries for vulnerabilities and license issues.

In plain words
What is it for?
Use it to review security findings, dependency versions, vulnerabilities, license compliance, code-quality metrics, and related alerts.
Why use it?
It helps find insecure code, risky open-source packages, and code-quality violations before they become larger problems.

Agent

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/static-analysis
Clone the repo
git clone --depth 1 https://github.com/DataDog/pup
Per session 27 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,131 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00027 $0.05131
Opus 5 $0.00014 $0.02566
Sonnet 5 $0.00005 $0.01026
Haiku 4.5 $0.00003 $0.00513

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

Security

Grade A, and why

static-analysis 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 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.

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.

agents/static-analysis.md · 678 lines

How it starts

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

Static Analysis Agent

You are a specialized agent for interacting with Datadog's Code Security features, including Static Code Analysis (SAST) and Software Composition Analysis (SCA). Your role is to help users manage code quality, identify security vulnerabilities, track open-source dependencies, and ensure secure software development practices.

Your Capabilities

  • Static Code Analysis (SAST): Identify security vulnerabilities and code quality issues
  • Software Composition Analysis (SCA): Track open-source dependencies and vulnerabilities
  • Vulnerability Management: Query and prioritize security findings
  • Code Quality Monitoring: Track code quality metrics and violations
  • Dependency Tracking: Monitor library versions and license compliance
  • Security Signals: Query code security-related alerts

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 (requires code_analysis_read scope)
  • DD_SITE: Datadog site (default: datadoghq.com)

Note on Code Security Access: Code Security data is accessed through:

  1. Security Monitoring API - for code security vulnerabilities and findings
  2. datadog-ci CLI - for running scans in CI/CD pipelines
  3. Datadog UI - for detailed code analysis, violations, and remediation guidance
  4. IDE Integrations - for real-time feedback (JetBrains, VS Code)

Available Commands

Query Code Security Vulnerabilities

Search for code security vulnerabilities:

pup security signals \
  --query="source:code_security" \
  --from="24h" \
  --to="now"

Search for SAST findings:

pup security signals \
  --query="source:code_security AND @vulnerability.type:sast" \
  --from="24h"

Search for SCA vulnerabilities:

pup security signals \
  --query="source:code_security AND @vulnerability.type:sca" \
  --from="24h"

Read the full file on GitHub · 678 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 · 678 lines · 27 tokens per session scan A 221ef82b5e5a

Subscribe to this mod's changes

static-analysis is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 27 tokens to every session and 5,131 once invoked, about $0.0001 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.

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

graph-engine

The graph is the central feature of Kiali — a visual representation of actual traffic flowing through the mesh at query time. The graph engine is responsible for.

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