stackhawk-hawkscan-cli

A set of instructions for using HawkScan, StackHawk's command-line web security scanner, during local development and automated builds.

In plain words
What is it for?
Use it to initialize HawkScan, run local or CI/CD security scans, validate configuration, inspect diagnostics, and manage scan options.
Why use it?
It clarifies which scan command to use, how credentials are found, and how to configure scans for agent workflows and log parsing.

Cursor rule for Cursor

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 rules/stackhawk/agent-skills/stackhawk-hawkscan-cli
Clone the repo
git clone --depth 1 https://github.com/stackhawk/agent-skills

Made for: Cursor.

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,437 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.00057 $0.02437
Opus 5 $0.00028 $0.01218
Sonnet 5 $0.00011 $0.00487
Haiku 4.5 $0.00006 $0.00244

Measured 2d ago against content hash 4bab2323a5f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

stackhawk-hawkscan-cli 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.

cursor/.cursor/rules/stackhawk-hawkscan-cli.mdc · 274 lines

How it starts

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

HawkScan CLI Reference

The hawk CLI is preferred for local/agentic use — lower overhead than Docker, faster iteration on config, and better localhost networking.

Option resolution order: CLI flag → API_KEY environment variable → ~/.hawk/hawk.properties. For local/agentic use, run hawk init --browser to write credentials to ~/.hawk/hawk.properties — no env var needed. For CI/CD pipelines, prefix invocations with API_KEY=$HAWK_API_KEY hawk ....

Contents


Top-Level Options

These go before the command (hawk [options] <command>):

hawk scan                                # after `hawk init --browser` — credentials from ~/.hawk/hawk.properties
hawk --no-color scan                     # strip ANSI escape codes (required for log parsing)
hawk --num-stored-sessions=4 scan        # number of sessions to keep (default: 4)
hawk --log-roll-size=100MB scan          # log file roll size (default: 100MB)
hawk --log-files-count=10 scan           # max rolled log files to upload (default: 10)

Setup

hawk init --browser                      # first-time: browser device-flow auth, saves to ~/.hawk/hawk.properties
API_KEY=$HAWK_API_KEY hawk scan          # CI/CD: pass key directly when no local config (pipelines, Docker)

Core Scan Commands

hawk scan                                          # scan using stackhawk.yml in current directory
hawk scan stackhawk-ci.yml                         # scan with a specific config file
hawk scan base.yml override.yml                    # merge configs (later file wins)
hawk rescan                                        # re-run plugins that fired on the most recent scan
hawk rescan --scan-id <SCAN_ID>                    # re-run plugins against a specific prior scan
hawk rescan --scan-id <SCAN_ID> --json-output      # rescan + structured output for parsing

Read the full file on GitHub · 274 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. 2d ago First seen · 274 lines · 57 tokens per session scan A 4bab2323a5f2

Subscribe to this mod's changes

stackhawk-hawkscan-cli is a cursor rule published in the GitHub repository stackhawk/agent-skills (15 stars, last pushed 12d ago), licensed MIT. It adds 57 tokens to every session and 2,437 once invoked, about $0.0003 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.