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-hawkscan-ci-app-startup)<a href="https://agentmods.dev/rules/stackhawk/agent-skills/stackhawk-hawkscan-ci-app-startup"><img src="https://agentmods.dev/badge/rules/stackhawk/agent-skills/stackhawk-hawkscan-ci-app-startup/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-hawkscan-ci-app-startup"><img src="https://agentmods.dev/badge/rules/stackhawk/agent-skills/stackhawk-hawkscan-ci-app-startup.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.00070 | $0.03072 |
| Opus 5.5 | $0.00028 | $0.01229 |
| Sonnet 5.5 | $0.00014 | $0.00614 |
| Haiku 4.5 | $0.00007 | $0.00307 |
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 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.
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' 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--buildonly rebuilds services that have abuild:stanza — a service defined purely byimage:ignores it), or add abuild: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.
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 · 216 lines · 70 tokens per session scan A f3a3b016d37d
stackhawk-hawkscan-ci-app-startup is a cursor rule published in the GitHub repository stackhawk/agent-skills (16 stars, last pushed 8d ago), licensed MIT. It adds 70 tokens to every session and 3,072 once invoked, about $0.0003 per session on Opus 5.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.
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).