A plugin that adds StackHawk HawkScan, a web-application security scanner, to an automated CI/CD pipeline. CI/CD systems automatically build, test, and deploy code, and the plugin supports several common providers.

Use it to detect supported CI configurations, edit pipeline files, add a HawkScan job, and choose where the scanner key should be stored.

It removes the manual work of finding the pipeline configuration and adding a security-scan job. It also guides storage of the required HAWK_API_KEY in a secrets store.

hawkscan-ci — Plugin by stackhawk

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.

Claude Code

/plugin marketplace add stackhawk/agent-skills

agentmods

npx agentmods add plugins/stackhawk/agent-skills/hawkscan-ci

Clone the repo

git clone --depth 1 https://github.com/stackhawk/agent-skills

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

hawkscan-ci 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 2d ago.

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.

plugins/hawkscan-ci/.claude-plugin/plugin.json · 26 lines

What it actually says

{
  "name": "hawkscan-ci",
  "version": "2.5.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"
  ]
}

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.

2d ago First seen · 26 lines scan A 4cf25991676b

Subscribe to this mod's changes

hawkscan-ci is a plugin published in the GitHub repository stackhawk/agent-skills (15 stars, last pushed 12d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

DevOps and cloud Security Testing

hawkscan-ci

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc

ecc