Borrowing it
Nothing to install: this file belongs to konstruktoid/hardened-images. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/konstruktoid/hardened-images/master/.github/instructions/github-actions.instructions.mdgit clone --depth 1 https://github.com/konstruktoid/hardened-imagesWrote 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/instructions/konstruktoid/hardened-images/github-actions)<a href="https://agentmods.dev/instructions/konstruktoid/hardened-images/github-actions"><img src="https://agentmods.dev/badge/instructions/konstruktoid/hardened-images/github-actions/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/instructions/konstruktoid/hardened-images/github-actions"><img src="https://agentmods.dev/badge/instructions/konstruktoid/hardened-images/github-actions.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.00586 | $0.00586 |
| Opus 5.5 | $0.00234 | $0.00234 |
| Sonnet 5.5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
hardened-images github-actions.instructions.md 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.
- Avoid curl-pipe-to-shell patterns; download, verify, then execute. How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise GitHub Actions Security Instructions
Apply these rules to workflow and action definitions.
Security-first workflow design
- Use least-privilege
permissionsat workflow/job scope; avoid implicit broad defaults. - Keep triggers narrow (
branches,paths, event types) and avoid unnecessary execution scope. - Pin third-party actions to commit SHA (with a version comment), as already done in this repo's workflows.
- Treat all PR metadata, artifact contents, and external inputs as untrusted.
- Use
step-security/harden-runner(or equivalent) at the start of jobs that build/release artifacts.
Secrets and token handling
- Never hardcode secrets or tokens.
- Use GitHub secrets/variables and mask sensitive output.
- Avoid printing env/context objects that may contain credentials.
- Minimize
GITHUB_TOKENprivileges and step exposure. - Azure service principal credentials (
ARM_*) must never appear in workflow logs or be persisted as artifacts.
High-risk event and runner handling
- Use extreme caution with
pull_request_targetandworkflow_run; never execute untrusted code with elevated context. - For self-hosted runners, enforce strict trust boundaries, labeling, and job scoping.
- Validate artifact provenance before reuse; avoid cross-trust artifact promotion.
- Treat caches as potentially attacker-influenced; scope keys defensively.
- SLSA provenance generation (
slsa.yml) and itspermissions/id-tokenscoping must not be broadened beyond what the release job needs.
Reliability and safety defaults
- Set explicit
timeout-minutes. - Use
concurrencyto prevent unsafe overlap when deployments/stateful steps exist. - Keep scripts short, fail-fast, and explicit (
set -euo pipefailfor bash steps where appropriate). - Avoid curl-pipe-to-shell patterns; download, verify, then execute.
Review priorities
- Privilege model (
permissions, token use, OIDC scope) - Trigger safety and untrusted input handling
- Third-party dependency trust (pinning, provenance)
- Secret exposure risks in logs, outputs, artifacts, and caches
- Runner isolation and escalation paths
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 · 51 lines · 586 tokens per session scan A db67b5ab3d96
hardened-images github-actions.instructions.md is an instructions file published in the GitHub repository konstruktoid/hardened-images (93 stars, last pushed yesterday), licensed Apache-2.0. It adds 586 tokens to every session, about $0.0023 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.