What is containerization-assist AGENTS.md?

A set of instructions for agents working on a TypeScript project that produces both ESM and CommonJS builds. These are two ways JavaScript modules can be packaged for different runtimes.

Use it before pushing changes to run the full build or both TypeScript checks, while avoiding incompatible patterns such as using import.meta in code that must compile as CommonJS.

It prevents code from passing a local check while failing the separate CommonJS build used by continuous integration, the automated system that checks changes.

containerization-assist AGENTS.md — Instructions file by Azure

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/azure/containerization-assist/agents-md

Clone the repo

git clone --depth 1 https://github.com/Azure/containerization-assist

Made for: Codex, OpenCode.

Per session 435 This file is loaded in full into every session.

When invoked 435 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.

Model	Per session	Once invoked
Fable 5	$0.00435	$0.00435
Opus 5	$0.00217	$0.00217
Sonnet 5	$0.00087	$0.00087
Haiku 4.5	$0.00044	$0.00044

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

Security

Grade A, and why

containerization-assist AGENTS.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.

AGENTS.md · 47 lines

What it actually says

Agent Instructions

Instructions for AI coding agents working on this repository.

Build Verification Before Pushing

This project produces two build targets (ESM and CJS) with different TypeScript configs. The local npm run typecheck only checks the ESM build (tsconfig.json). CI also builds CJS (tsconfig.cjs.json with "module": "commonjs"), which has different constraints (e.g. import.meta is not allowed).

Always verify both builds pass before pushing:

npm run build

This runs: clean -> build:version -> build:knowledge -> build:policies -> build:esm -> build:cjs

If a full build is too slow, at minimum check both TypeScript compilations:

npm run build:version && npm run build:knowledge && npx tsc -p tsconfig.json --noEmit && npx tsc -p tsconfig.cjs.json --noEmit

Common pitfalls

import.meta compiles under ESM (tsconfig.json, "module": "ES2022") but fails under CJS (tsconfig.cjs.json, "module": "commonjs"). Avoid it in src/ code.
__dirname / require() work in CJS but are not available at ESM runtime.
Generated files (src/lib/generated-version.ts, src/knowledge/embedded-packs.ts) are gitignored and created by build steps. They must exist before typecheck or tests. Run npm run build:version to generate the version file.

Running Tests

npm test                # unit + integration + e2e (auto-runs build:version)
npm run test:unit       # unit tests only

Code Style

TypeScript strict mode is enabled
Formatting: Prettier (npm run format:check)
Linting: ESLint (npm run lint)

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.

2d ago First seen · 47 lines · 435 tokens per session scan A 2d0b448da69d

Subscribe to this mod's changes

containerization-assist AGENTS.md is an instructions file published in the GitHub repository Azure/containerization-assist (41 stars, last pushed 13d ago), licensed MIT. It adds 435 tokens to every session, about $0.0022 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.

DevOps and cloud

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

microsoft/vscode · 6,785 tokens

containerization-assist AGENTS.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Agent Instructions

Build Verification Before Pushing

Common pitfalls

Running Tests

Code Style

What this file has done since we first saw it

Other instructions, from other repositories

vscode buildNext.instructions.md

spec-kit AGENTS.md

codex AGENTS.md

langchain AGENTS.md

vscode oss-third-party-notices.instructions.md

next.js AGENTS.md