Skip to content
TrustedSkillsbeta
Back to all skills

Defender For Devops

Checked
josiahsiegel·vlatest·devops·MIT

Automates incident response & remediation tasks, proactively identifying and resolving DevOps pipeline issues.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add josiahsiegel/claude-plugin-marketplace --skill defender-for-devops -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

josiahsiegel

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a1b1123b9
Manifest
plugins/ado-master/skills/defender-for-devops/SKILL.md
Scanned
1 file, 433 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The defender-for-devops skill acts as a security gatekeeper for DevOps workflows, ensuring that infrastructure-as-code changes and deployment actions adhere to established safety protocols before execution. It integrates directly into development pipelines to validate configurations against known vulnerabilities and policy violations in real-time.

When to use it

  • Before committing sensitive environment variables or credentials to version control systems.
  • During the CI/CD pipeline stage prior to automated testing or production deployment.
  • When reviewing infrastructure-as-code templates for potential misconfigurations.
  • To enforce organizational security compliance standards on dynamic cloud resource provisioning.

Key capabilities

  • Real-time validation of DevOps scripts and configurations against security policies.
  • Detection of common vulnerabilities in infrastructure definitions before they are applied.
  • Prevention of unauthorized or risky changes from reaching production environments.
  • Integration with existing CI/CD workflows to block non-compliant deployments automatically.

Example prompts

  • "Run a security scan on this Terraform configuration file before I commit it to the repository."
  • "Validate these Kubernetes manifest changes against our organization's hardening guidelines."
  • "Check if this deployment script includes any hardcoded secrets or insecure API endpoints."

Tips & gotchas

Ensure your infrastructure-as-code files are properly formatted and contain all necessary context for the scanner to perform an accurate analysis. This skill is most effective when integrated early in the development lifecycle rather than as a post-deployment audit tool.