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.
npx agentmods add rules/stackhawk/agent-skills/stackhawk-optimize-mappinggit clone --depth 1 https://github.com/stackhawk/agent-skillsWhat 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 | $0.00059 | $0.00448 |
| Opus 5 | $0.00030 | $0.00224 |
| Sonnet 5 | $0.00012 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
stackhawk-optimize-mapping 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.
What it actually says
Codebase → Config Mapping
Tech flags
Reuse the hawkscan skill's tech-flag detection heuristics (linked from the Companion
skills section of SKILL.md) — evidence files such as package.json, pom.xml, go.mod,
requirements.txt, docker-compose.yml, Gemfile, *.csproj/*.sln.
Map detected techs to canonical flag keys. The canonical flag list is authoritative — fetch
it with hawk op app tech-flags get --app <APP> --format json and only use keys that exist.
When enabling a child flag (e.g. Language.Java.Spring), also enable its parents.
Plugins
Start from a base preset that matches the app shape:
- Plain REST/HTML app →
DEFAULT - OpenAPI-described API →
DEFAULT_API - GraphQL API → the GraphQL preset (confirm exact name via
hawk op policy list)
Fetch the base with hawk op policy get --name <PRESET>. Then:
- DROP plugin families irrelevant to the detected stack (reduces noise + time).
- KEEP/ADD families the stack needs. Validate every plugin id against the base policy's plugin list — never invent ids.
stackhawk.yml correctness
- App type: SPA → enable SPA/spider settings; REST → leave spider conservative.
- OpenAPI spec present → set
app.openApiConfto point at it. - GraphQL → consider
app.autoPolicy: true. - Base paths → set sensible scope.
- Auth → FLAG for the user; never fabricate credentials.
Profile lean
Default balanced. A speed lean drops more borderline plugin families and tightens scope; a coverage lean keeps families when in doubt. Only deviate from balanced if the user explicitly asks.
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 · 39 lines · 59 tokens per session scan A 44cc50efeb0d
stackhawk-optimize-mapping is a cursor rule published in the GitHub repository stackhawk/agent-skills (15 stars, last pushed 12d ago), licensed MIT. It adds 59 tokens to every session and 448 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.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.