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 instructions/tfutils/tfscaffold/bashgit clone --depth 1 https://github.com/tfutils/tfscaffoldWhat 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.00850 | $0.00850 |
| Opus 5 | $0.00425 | $0.00425 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
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.
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 useset -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 withset -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_diefor 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
localfor 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-getopton macOS) - Scripts should work with bash 3.2+ (macOS default) where possible
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.
- 2d ago First seen · 100 lines · 850 tokens per session scan A 62cab9b5983b
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.
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.
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).
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.
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
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.
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.