stackhawk-optimize-cli

A rule set for using the Hawk security-scanning command-line tool to manage scan policies and inspect scan metrics. A command-line tool is software operated by typing commands in a terminal.

In plain words
What is it for?
Use it to list, read, create, delete, or assign scan policies, read application technology settings, and review scan results by path.
Why use it?
It gives the surrounding skill the exact commands, options, and JSON output expectations needed to operate Hawk consistently.

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

Made for: Cursor.

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 445 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.00042 $0.00445
Opus 5 $0.00021 $0.00222
Sonnet 5 $0.00008 $0.00089
Haiku 4.5 $0.00004 $0.00044

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

Security

Grade A, and why

stackhawk-optimize-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-optimize-cli.mdc · 28 lines

What it actually says

hawk op CLI Contract (commands this skill calls)

Purpose Command
List policies (find base preset names) hawk op policy list --format json
Fetch a base policy as JSON hawk op policy get --name <PRESET>
Create/upsert a trial or permanent policy hawk op policy create --file <json> --name <NAME> [--display-name <DN>] [--dry-run]
Delete a policy hawk op policy delete --name <NAME> --yes [--dry-run]
(Optional) set app default hawk op policy assign --app <NAME|UUID> --name <NAME> [--dry-run]
Read canonical tech flags hawk op app tech-flags get --app <APP> --format json
Get per-path scan metrics + signal flags hawk op scan metrics <SCAN_ID|latest> [--sort heaviest|slowest|erroring|most-requested] [--top N] [--method <VERB>] [--operations] --format json

Notes:

  • policy get prints a full ScanPolicy JSON (tech flags + plugins) suitable for editing and re-submitting via policy create --file.
  • Policy names must match ^[A-Z0-9_]+$, ≤256 chars.
  • All write commands support --dry-run; use it in preflight to detect missing permissions/feature flags without making changes.
  • scan metrics --format json returns MetricsJson (paths[] with metrics + flags, operations[], request_health, scan_flags). The skill consumes this in the post-scan refine loop (see metrics-and-refine.md); it does not recompute metrics.
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 · 28 lines · 42 tokens per session scan A 7c5e06543b30

Subscribe to this mod's changes

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