tfscaffold bash.instructions.md

A set of house rules for writing Bash shell scripts in the tfutils/tfscaffold project. Bash is a command-line language commonly used to automate tasks on Linux and macOS.

In plain words
What is it for?
Use it before creating or changing Bash scripts to check the required shell setup, variable style, quoting, formatting, and file modeline.
Why use it?
It keeps scripts consistent and reduces mistakes involving unsafe shell settings, quoting, variables, formatting, and indentation.

Instructions file for GitHub Copilot

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 instructions/tfutils/tfscaffold/bash
Clone the repo
git clone --depth 1 https://github.com/tfutils/tfscaffold

Made for: GitHub Copilot.

Per session 850 This file is loaded in full into every session.
When invoked 850 The same file — it is already loaded in full.
Security scan A 0 findings. 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.00850 $0.00850
Opus 5 $0.00425 $0.00425
Sonnet 5 $0.00170 $0.00170
Haiku 4.5 $0.00085 $0.00085

Measured 2d ago against content hash 62cab9b5983b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tfscaffold bash.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 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.

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.

.github/instructions/bash.instructions.md · 100 lines

How it starts

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

Bash Coding Standards — tfscaffold

These standards apply to ALL bash scripts in the tfscaffold repository. Read this entire document BEFORE writing or modifying any bash code.

Mandatory Pre-Write Verification

Before writing ANY bash code, verify you understand these rules. Violations caught after writing waste time — get it right first.

Shell Setup

#!/usr/bin/env bash
set -uo pipefail;
  • Shebang: #!/usr/bin/env bash (exact format)
  • Strict mode: set -uo pipefail; — NEVER use set -e

Indentation and Formatting

  • 2-space indentation throughout (no tabs)
  • Terminate ALL statements with a semicolon (;) where syntactically correct
  • Include vim modeline at end of new scripts: # vim:set et ts=2 sw=2:

Variables

  • ALL variable references use braces: ${variable} (never $variable)
  • Script-local variables use lowercase: ${version}, ${region}
  • Environment variables use UPPERCASE: ${AWS_DEFAULT_REGION}, ${TF_VAR_region}
  • Always quote variable expansions: "${variable}"
  • Quote entire strings containing variables: "${dir}/file" NOT "${dir}"/file
  • Use ${var:-default} for optional variables (scripts run with set -u)

Quoting

  • Single-quote strings unless variable expansion is needed
  • Double-quote strings that contain variable expansion
  • NEVER use unescaped ! inside double-quoted strings (bash history expansion)

Command Substitution

  • Use $(...) NOT backticks

Error Handling

  • NEVER use set -e — handle errors explicitly
  • Use the project's existing error patterns:
    • error_and_die for fatal errors with optional exit code:
      error_and_die "Something went wrong";
      error_and_die "Bad input" 2;
      
    • Inline || pattern for simple cases:
      some_command || error_and_die "Failed to do thing";
      

Functions

  • Define as: function name() { ... };
  • Use local for variables inside functions

Cross-Platform Considerations

  • macOS uses BSD sed/grep/readlink — GNU extensions may not be available
  • tfscaffold requires GNU getopt (brew install gnu-getopt on macOS)
  • Scripts should work with bash 3.2+ (macOS default) where possible

Read the full file on GitHub · 100 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 · 100 lines · 850 tokens per session scan A 62cab9b5983b

Subscribe to this mod's changes

tfscaffold bash.instructions.md is an instructions file published in the GitHub repository tfutils/tfscaffold (281 stars, last pushed 4mo ago), licensed MIT. It adds 850 tokens to every session, about $0.0042 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.

Related

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens