Sysdig Headless Cloud Security

Summary

Sysdig’s cloud security expertise, packaged as agent skills that work natively in your AI environment.

Description

Headless Cloud Security brings Sysdig’s runtime-grounded security knowledge directly into Claude, so security teams can onboard, investigate, and operate cloud security workflows without leaving their AI environment.

Built for enterprises that have adopted coding agents as part of their standard toolchain, Headless Cloud Security packages over a decade of cloud security expertise as reusable skills covering environment onboarding, vulnerability management, risk analysis, and runtime threat investigation. Every action is designed to keep humans in control, with structured logging for full auditability.

Sysdig’s runtime layer, powered by Falco, provides the high-fidelity, deterministic signals that make agent-driven security workflows trustworthy. The platform adapts to how your security program operates, not the other way around.

Terms

Use of the Sysdig Headless Cloud Security plugin (the “Plugin”) is governed by the Sysdig Artificial Intelligence Addendum and Acceptable Use Policy, incorporated into the agreement between Customer and Sysdig.

The Plugin incorporates agentic artificial intelligence, which may act autonomously or semi-autonomously based on Customer prompts, configured parameters, permissions, policies, and instructions to generate outputs, make recommendations, make decisions, or take actions on Customer’s behalf. Customer is solely responsible for: (i) reviewing, validating, monitoring, and supervising all outputs, decisions, recommendations, and actions generated or taken by the Plugin; and (ii) ensuring the accuracy, completeness, legality, appropriateness, and security of any resulting outputs, actions, or downstream effects.

How to use

Once installed, describe what you need in plain language. Examples:

• “Onboard my AWS account to Sysdig”
• “Show me the highest-risk vulnerabilities in production”
• “Investigate this runtime alert and tell me if it’s exploitable”

Prerequisites

• A Sysdig Secure account
• A supported AI coding agent — Claude Code is the primary target; Cursor, OpenAI Codex, and OpenCode can use the bare skills via Compatibility with other agents
• Python 3 — required by skill scripts (uses stdlib only, no pip install needed)
• A Sysdig API token — only if you use sysdig-onboarding or sysdig-posture. Generate one under Settings → Sysdig Secure API. Every other skill authenticates via OAuth and needs no token.

Install in Claude Code

/plugin marketplace add sysdig/skills

/plugin install headless-cloud-security@sysdig-skills

The marketplace install loads the plugin skills and any per-skill MCP server dependencies declared in agents/*.yaml. The hosted Sysdig MCP server is not bundled — register it separately (next step).

Register the Sysdig MCP server

Most skills reach your tenant through the hosted Sysdig MCP server, authenticated with OAuth — there is no token to copy. Register it once, pointing at your region’s MCP URL (your region URL + /mcp/secure):

claude mcp add --transport http secure-mcp-server https://us2.app.sysdig.com/mcp/secure

Replace us2.app.sysdig.com with your region URL from the table below — the MCP URL is always your region URL + /mcp/secure. Then run /mcp → secure-mcp-server → Authenticate for the one-time OAuth sign-in. Once authenticated, describe what you need in plain language and the right skill loads automatically.

Sysdig region URLs:

If your region isn’t listed, the hosted MCP server isn’t available there yet — contact your Sysdig representative about availability. If it is listed, other agents (Cursor, OpenAI Codex, OpenCode, Claude Desktop, ChatGPT, Gemini, …) can register the same server: an HTTP MCP server at your region’s /mcp/secure URL, with OAuth — see each skill’s references/mcp-setup.md.

API token — only for some skills

sysdig-onboarding and sysdig-posture call the Sysdig REST API or Terraform provider directly, so they need a token in your environment. (Every other skill uses OAuth — skip this section.) Export it in your shell profile, using your region URL from the table above:

export SYSDIG_SECURE_URL="https://us2.app.sysdig.com"     # your Sysdig region URL
export SYSDIG_SECURE_API_TOKEN="your-api-token"

Skills auto-discover these. Never paste credentials in chat. The hosted MCP server ignores these variables.

Compatibility with other agents

Every skill follows the Agent Skills specification and is published as a stand-alone unit under skills// at the repo root. These bare-skill copies are kept in sync with the plugin contents on every publish, so they always reflect the latest released skill set.

Install with npx skills (recommended)

The skills CLI works with any spec-compliant agent. To install a single skill:

npx skills install sysdig/skills 

For example, to install the onboarding skill:

npx skills install sysdig/skills sysdig-onboarding

npx skills reads each skill’s SKILL.md and copies it (along with its scripts and references) into the appropriate skills directory for your agent.

Manual install (clone and symlink)

If you prefer to manage the files yourself:

git clone https://github.com/sysdig/skills.git ~/sysdig-skills

# Example: link every published skill into your agent's skills directory
ln -s ~/sysdig-skills/skills/* /

MCP server registration

The Sysdig MCP server is never bundled — you register it yourself with claude mcp add (see Register the Sysdig MCP server above) regardless of install method. Per-skill agents/*.yaml dependencies on other MCP servers (Jira, GitHub, …) are also not loaded by either of the two methods above; register those with your agent yourself too.

Skills shipped today

The list above is generated automatically on every publish from each skill’s SKILL.md frontmatter.

Repository layout

skills/
├── .claude-plugin/
│   └── marketplace.json                  # marketplace index (generated)
├── plugins/
│   └── headless-cloud-security/          # the published Claude Code plugin
│       ├── .claude-plugin/plugin.json
│       └── skills//          # one directory per skill
└── skills/
    └── /                     # bare-skill mirror (spec-compliant)

Scanning these skills with SkillSpector

If you audit agent skills with SkillSpector, this repository ships a reviewed baseline (.skillspector-baseline.yaml) that suppresses known false positives and intended-by-design findings, each with an explanation. Pass it so only new or genuinely actionable findings surface:

# Scan one skill with the shipped baseline (scan per-skill —
# SkillSpector's --recursive mode does not apply --baseline).
skillspector scan skills/ --baseline .skillspector-baseline.yaml

The baseline is also copied inside each skill directory, so a single-skill install still carries it:

skillspector scan skills/ --baseline skills//.skillspector-baseline.yaml

Suppressed findings are reported as suppressed (with their justification) rather than dropped silently — for example, threat-detection documentation that references attacker techniques (IMDS endpoints, credential paths), the intentionally privileged Sysdig host agent, and documented credential auto-discovery from SYSDIG_* environment variables. Findings not in the baseline are real and worth reviewing.

Maintenance and contributions

This repository is published and maintained by Sysdig through an automated pipeline. Direct pull requests are not accepted — any direct changes will be overwritten on the next publish. See CONTRIBUTING.md.

Reporting security issues

Do not disclose security findings in public forums. Email [email protected] with details.

License

See LICENSE.