Agent Plugins Marketplace
← All plugins

hawkscan-ci

v2.7.0

Configure HawkScan in your CI/CD pipeline. Provider-agnostic: detects GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines, Bitbucket, Buildkite, and other CI systems from repo files, edits the pipeline file in place to add a HawkScan job, and prompts for HAWK_API_KEY storage (CI-native secrets store or external secrets manager).

CodexClaude Code1 Skill

By StackHawkLicense: MIT16 GitHub starsUpdated last week

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
1 skill or MCP entry
Source updated
Oct 9, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install hawkscan-ci for Codex and Claude Code

Installs for the current user
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add hawkscan-ci@agent-plugin-marketplace

Paste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/stackhawk/agent-skills

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/hawkscan-ci/.

Plugin files

plugins/hawkscan-ci/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
└── skills/hawkscan-ci/SKILL.md

Included Skills1

hawkscan-ciskills/hawkscan-ci/SKILL.md

Use when the user wants to WIRE HawkScan into a CI/CD pipeline config file — triggers on "set up hawkscan in CI", "add stackhawk to my pipeline", "scan in CI", "configure github actions / gitlab / jenkins / circleci for hawkscan", "wire hawkscan into ci/cd", or any provider-named variant. Provider-agnostic: detects the CI system from repo files, edits the pipeline file in place to add a HawkScan job, prompts for HAWK_API_KEY storage in the CI's native secrets store (or an approved external manager), and wires commit-SHA + branch traceability. If no local stackhawk.yml exists yet, still trigger and route the local-config work to the hawkscan skill. Do NOT trigger for: documentation-only changes (e.g. editing a README about CI scanning); informational or research questions ("what CI providers does HawkScan support?"); or running / performing a scan — a local scan is the hawkscan skill, whereas this skill only edits CI pipeline config. Explicit trigger only; no autonomous code-change hook.

Plugin manifests2

plugins/hawkscan-ci/.codex-plugin/plugin.json
{
  "name": "hawkscan-ci",
  "version": "2.7.0",
  "description": "Configure HawkScan in your CI/CD pipeline. Provider-agnostic: detects GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines, Bitbucket, Buildkite, and other CI systems from repo files, edits the pipeline file in place to add a HawkScan job, and prompts for HAWK_API_KEY storage (CI-native secrets store or external secrets manager).",
  "author": {
    "name": "StackHawk",
    "email": "[email protected]",
    "url": "https://www.stackhawk.com"
  },
  "homepage": "https://docs.stackhawk.com/integrations/ci-cd/",
  "repository": "https://github.com/stackhawk/agent-skills",
  "license": "MIT",
  "keywords": [
    "security",
    "dast",
    "appsec",
    "hawkscan",
    "stackhawk",
    "ci-cd",
    "github-actions",
    "gitlab-ci",
    "jenkins",
    "pipeline"
  ],
  "skills": "./skills/"
}
plugins/hawkscan-ci/.claude-plugin/plugin.json
{
  "name": "hawkscan-ci",
  "version": "2.7.0",
  "description": "Configure HawkScan in your CI/CD pipeline. Provider-agnostic: detects GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines, Bitbucket, Buildkite, and other CI systems from repo files, edits the pipeline file in place to add a HawkScan job, and prompts for HAWK_API_KEY storage (CI-native secrets store or external secrets manager).",
  "author": {
    "name": "StackHawk",
    "email": "[email protected]",
    "url": "https://www.stackhawk.com"
  },
  "homepage": "https://docs.stackhawk.com/integrations/ci-cd/",
  "privacyPolicyUrl": "https://www.stackhawk.com/privacy-policy/",
  "termsOfServiceUrl": "https://www.stackhawk.com/terms-of-service/",
  "supportUrl": "https://docs.stackhawk.com/support/",
  "documentationUrl": "https://docs.stackhawk.com/ai-security/agent-skills/",
  "repository": "https://github.com/stackhawk/agent-skills",
  "license": "MIT",
  "keywords": [
    "security",
    "dast",
    "appsec",
    "hawkscan",
    "stackhawk",
    "ci-cd",
    "github-actions",
    "gitlab-ci",
    "jenkins",
    "pipeline"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[hawkscan-ci on Agent Plugins Marketplace](https://pluginsmp.com/plugins/hawkscan-ci)