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/packer-shell.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/packer-shell)<a href="https://agentmods.dev/instructions/konstruktoid/hardened-images/packer-shell"><img src="https://agentmods.dev/badge/instructions/konstruktoid/hardened-images/packer-shell.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.1 | $0.00970 | $0.00970 |
| Opus 5 | $0.00485 | $0.00485 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
hardened-images packer-shell.instructions.md 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Packer and Shell Provisioning Instructions
Apply these rules to Packer templates and the shell scripts that build and provision the hardened images.
Shell scripting requirements
- Start scripts with
set -euo pipefail(or equivalent explicit error handling) so failures during a build stop the pipeline rather than continuing silently. - Must pass
shellcheck(enforced via.pre-commit-config.yaml, theshelljob in.github/workflows/lint.yml, andbuild_box.shitself); fix findings rather than disabling checks. When a suppression is genuinely correct, use a targeted# shellcheck disable=SCxxxxwith a comment saying why. azure_vars_exportis sourced, not executed. It must not useset -e, which would terminate the caller's interactive shell; it handles errors explicitly andreturns instead.- Quote variables and paths; avoid word-splitting/glob bugs on user-supplied
input (e.g.
-varoverrides passed tobuild_box.sh). - Never persist Azure
ARM_*credentials or other secrets to disk; only export them into the current shell's environment.
Packer template requirements
- Keep
*.pkr.hcldeclarative — provisioning logic belongs inscripts/orconfig/local.yml, not inline shell embedded in HCL. - Pin
required_versionfor Packer core and every entry inrequired_pluginsto an exact minor series (~> 1.1.6), mirroring the existing templates. A floating>=constraint is not a pin. - Templates must be
packer fmtclean and mustpacker validate. Both are enforced by thepackerjob in.github/workflows/lint.yml, andbuild_box.shrunspacker validatebeforepacker build. - Mark credential variables
sensitive = trueunless the value is a short common word, which Packer would then redact from unrelated build output. State the reason in a comment when leaving one unmarked. - Use
variable ... validationblocks for values whose absence would otherwise produce a silently wrong build, such as the IP address that scopes the Azure build VM's inbound SSH rule. - Provisioner scripts are
#!/bin/bashand rely on bash-only behaviour, soexecute_commandmust invokebash, notsh.
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.
- 8d ago First seen · 76 lines · 970 tokens per session scan A 00eb14372ee0
hardened-images packer-shell.instructions.md is an instructions file published in the GitHub repository konstruktoid/hardened-images (90 stars, last pushed today), licensed Apache-2.0. It adds 970 tokens to every session, about $0.0049 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.