stackhawk-hawkscan-ci-app-startup

Reference patterns for starting a web application in continuous integration before HawkScan tests it. Continuous integration is automated building and testing run by a code-hosting service or build server.

In plain words
What is it for?
Use it to choose a startup method for Docker Compose, Node, JVM, or Dockerfile projects, wait for health checks, scan preview deployments, and handle localhost access from containers.
Why use it?
It helps ensure the application is running and reachable before the security scan begins, while accounting for Docker networking and different project types.

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

Made for: Cursor.

Per session 70 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,072 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00070 $0.03072
Opus 5 $0.00035 $0.01536
Sonnet 5 $0.00014 $0.00614
Haiku 4.5 $0.00007 $0.00307

Measured 2d ago against content hash f3a3b016d37d, 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-ci-app-startup scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

timeout 60 bash -c 'until curl -fsS http://localhost:8080/health; do sleep 2; done'
cursor/.cursor/rules/stackhawk-hawkscan-ci-app-startup.mdc · 216 lines

How it starts

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

App Startup Patterns Reference

The scan target needs to be reachable from the CI runner before hawk scan runs. This reference catalogs the common patterns and their tradeoffs.

Pattern Selection

Repo signals Pattern
docker-compose.yml / compose.yml at root Docker Compose + wait-for-it
package.json with start / dev script Build-then-run (Node)
pom.xml or build.gradle* with Spring Boot Build-then-run (JVM)
Dockerfile only (no compose) Run image as background container
App already deployed to ephemeral env Scan-existing-host (no startup step)
None of the above Ask the user for the start command

Pattern 1 — Docker Compose

Most common; works on every provider that has Docker. Assume the compose file exposes the app on a known port (e.g., 8080).

docker compose up -d
# wait for app to be ready before scanning
timeout 60 bash -c 'until curl -fsS http://localhost:8080/health; do sleep 2; done'

Scan an artifact built from the commit under test. A PR scan should gate the code in this checkout. If the compose service for the app under test declares image: pointing at a published registry tag (e.g. :latest or :<branch>) with no build: block, docker compose up pulls whatever that tag currently is — which may have been built elsewhere from different code, so the scan gates a commit that isn't the one under review. Make sure the scanned image corresponds to this commit. Any of these are fine:

  • Build in the job: docker compose up -d --build (note --build only rebuilds services that have a build: stanza — a service defined purely by image: ignores it), or add a build: block via a compose override (docker-compose.override.yml).
  • Build → push → pull: build the image from this commit in an earlier step, push it, and point the compose image: at that exact tag or digest. Pulling is fine here — the tag was built from the commit under test.

The anti-pattern is scanning a published tag built elsewhere from different code, not "pulling" per se. Confirm the image under scan matches the commit before trusting the result.

Read the full file on GitHub · 216 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 · 216 lines · 70 tokens per session scan A f3a3b016d37d

Subscribe to this mod's changes

stackhawk-hawkscan-ci-app-startup is a cursor rule published in the GitHub repository stackhawk/agent-skills (16 stars, last pushed 12d ago), licensed MIT. It adds 70 tokens to every session and 3,072 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.