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.
git clone --depth 1 https://github.com/stackhawk/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/stackhawk/agent-skills/stackhawk-optimize-cli)<a href="https://agentmods.dev/rules/stackhawk/agent-skills/stackhawk-optimize-cli"><img src="https://agentmods.dev/badge/rules/stackhawk/agent-skills/stackhawk-optimize-cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/stackhawk/agent-skills/stackhawk-optimize-cli"><img src="https://agentmods.dev/badge/rules/stackhawk/agent-skills/stackhawk-optimize-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.00445 |
| Opus 5.5 | $0.00017 | $0.00178 |
| Sonnet 5.5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
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 1mo 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.
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 getprints a fullScanPolicyJSON (tech flags + plugins) suitable for editing and re-submitting viapolicy 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 jsonreturnsMetricsJson(paths[] with metrics + flags, operations[], request_health, scan_flags). The skill consumes this in the post-scan refine loop (seemetrics-and-refine.md); it does not recompute metrics.
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.
- 1mo ago First seen · 28 lines · 42 tokens per session scan A 7c5e06543b30
stackhawk-optimize-cli is a cursor rule published in the GitHub repository stackhawk/agent-skills (16 stars, last pushed 8d ago), licensed MIT. It adds 42 tokens to every session and 445 once invoked, about $0.0002 per session on Opus 5.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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).