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 skills/stackhawk/agent-skills/hawkscan-cinpx skills add stackhawk/agent-skills --skill hawkscan-cigit 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/skills/stackhawk/agent-skills/hawkscan-ci)<a href="https://agentmods.dev/skills/stackhawk/agent-skills/hawkscan-ci"><img src="https://agentmods.dev/badge/skills/stackhawk/agent-skills/hawkscan-ci.svg" alt="Measured on agentmods" 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 | $0.00232 | $0.04444 |
| Opus 5 | $0.00116 | $0.02222 |
| Sonnet 5 | $0.00046 | $0.00889 |
| Haiku 4.5 | $0.00023 | $0.00444 |
Grade A, and why
hawkscan-ci 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HawkScan CI Skill
This skill graduates a working local HawkScan setup into a CI/CD
pipeline. It is a wrapper around the local-scan path the hawkscan
skill owns — it never generates stackhawk.yml, never picks auth
recipes, never parses findings. Its scope is the pipeline file alone.
Hand-off rule: if stackhawk.yml doesn't exist or doesn't validate,
the agent must invoke the hawkscan skill first. This skill does not
onboard apps from scratch.
Step 0: Hand-off Check
Before doing anything CI-specific, confirm the local scan path is in place. Run:
test -f stackhawk.yml || echo "MISSING_CONFIG"
timeout 30 hawk validate config stackhawk.yml 2>&1 | head -20
If stackhawk.yml is missing, validation fails, or applicationId is
still a placeholder (${APP_ID} with no real value, or literal
your-app-id):
"I need a working local scan first. Run the hawkscan skill (or invoke it explicitly) to generate and validate
stackhawk.yml, then come back here."
Stop. Do not proceed.
Step 1: Detect the CI Provider
Glob the repo for known CI config locations:
ls .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null
ls .gitlab-ci.yml 2>/dev/null
ls Jenkinsfile* 2>/dev/null
ls .circleci/config.yml 2>/dev/null
ls azure-pipelines*.yml 2>/dev/null
ls bitbucket-pipelines.yml 2>/dev/null
ls .buildkite/pipeline.yml 2>/dev/null
ls .travis.yml 2>/dev/null
ls -d bamboo-specs 2>/dev/null
ls concourse/*.yml 2>/dev/null
ls -d harness 2>/dev/null
ls appspec.yml buildspec.yml 2>/dev/null
| Match | Provider |
|---|---|
.github/workflows/*.yml, *.yaml |
GitHub Actions |
.gitlab-ci.yml |
GitLab CI/CD |
Jenkinsfile, Jenkinsfile.* |
Jenkins |
.circleci/config.yml |
CircleCI |
azure-pipelines*.yml |
Azure Pipelines |
bitbucket-pipelines.yml |
Bitbucket Pipelines |
.buildkite/pipeline.yml |
Buildkite |
.travis.yml |
Travis CI |
bamboo-specs/ |
Bamboo |
appspec.yml, buildspec.yml |
AWS CodeBuild / CodeDeploy |
concourse/*.yml (heuristic — confirm with user) |
Concourse |
harness/ |
Harness |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 343 lines · 232 tokens per session scan A ec13922da70f
hawkscan-ci is a skill published in the GitHub repository stackhawk/agent-skills (16 stars, last pushed 14d ago), licensed MIT. It adds 232 tokens to every session and 4,444 once invoked, about $0.0012 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 skills, from other repositories
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
upgrading-golang
Upgrades Go version across the entire Chainloop codebase including source files, Docker images, CI/CD workflows, and documentation. Use when the user mentions upgrading Go, golang version, or updating Go compiler version.
python-canary-fix
Investigate and propose fixes for Python canary cron failures in the openinference repo. Use when the user mentions Python canary failures, Python cron failures, or when the auto-fix CI job reports Python instrumentation canary issues.
ci-fixer
CI failures - read error, minimal fix, verify.
infrastructure-setup
Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг"…