zapcode AGENTS.md

A set of repository instructions for Zapcode, a Rust-based interpreter that safely runs a limited version of TypeScript code produced by AI agents.

In plain words
What is it for?
Use it when developing, testing, or reviewing Zapcode and its Rust, TypeScript, Python, or WebAssembly integrations.
Why use it?
It explains the project’s purpose, structure, safety boundaries, supported interfaces, and resource limits before code is changed.

Instructions file for CodexOpenCode

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/theuncharted/zapcode/agents-md
Clone the repo
git clone --depth 1 https://github.com/TheUncharted/zapcode

Made for: Codex, OpenCode.

Per session 2,481 This file is loaded in full into every session.
When invoked 2,481 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.02481 $0.02481
Opus 5 $0.01241 $0.01241
Sonnet 5 $0.00496 $0.00496
Haiku 4.5 $0.00248 $0.00248

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

Security

Grade A, and why

zapcode 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 · 254 lines

How it starts

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

AGENTS.md

Standard agent instructions for the zapcode project. Read this before writing any code.


What this project is

Zapcode is a minimal, secure TypeScript subset interpreter written in Rust, designed specifically to execute code written by AI agents. It is the TypeScript equivalent of pydantic/monty.

The core thesis: LLMs produce faster, cheaper, more reliable results when they write code instead of making sequential tool calls. Zapcode makes that possible for TypeScript/JavaScript stacks without containers, sandbox services, or running untrusted code directly on the host.

What Zapcode can do:

  • Execute a safe subset of TypeScript — enough for an agent to express what it wants to do
  • Block all host access by default: filesystem, env vars, network, require, import
  • Expose host functions to the sandbox — only functions you explicitly register
  • Snapshot VM state to bytes at external function call boundaries — resume later in any process
  • Start in microseconds (~2 µs for simple expressions)
  • Be called from Rust, TypeScript/JavaScript (napi-rs), Python (PyO3), or WebAssembly
  • Enforce resource limits: memory, execution time, stack depth, allocation count

What Zapcode cannot do (by design):

  • Access the standard library beyond a safe subset (console, JSON, Math, Array, Object, Promise)
  • Use import / require / dynamic imports
  • Access process, globalThis, eval, Function(), setTimeout/setInterval
  • Use proxies, WeakMap/WeakRef, Symbol, or with statements
  • Execute regular expressions (parsed but execution is a no-op)
  • Use var declarations (use let/const)

Repository layout

zapcode/
├── crates/
│   ├── zapcode-core/       # Parser, IR, bytecode compiler, VM, snapshot
│   │   ├── src/
│   │   │   ├── parser/      # oxc_parser integration — AST → ZapcodeIR
│   │   │   │   ├── mod.rs   # AST walker (oxc → IR)
│   │   │   │   └── ir.rs    # IR type definitions
│   │   │   ├── compiler/    # ZapcodeIR → Bytecode
│   │   │   │   ├── mod.rs   # Compiler logic
│   │   │   │   └── instruction.rs  # Instruction enum (~55 opcodes)
│   │   │   ├── vm/          # Stack-based bytecode executor
│   │   │   │   ├── mod.rs   # VM main loop, dispatch, ZapcodeRun entry point
│   │   │   │   └── builtins.rs  # Built-in functions (console, Math, JSON, etc.)
│   │   │   ├── value.rs     # Value enum — runtime type system
│   │   │   ├── snapshot.rs  # Serialize/deserialize mid-execution VM state
│   │   │   ├── sandbox.rs   # Resource limits and tracking
│   │   │   ├── error.rs     # ZapcodeError — all error types
│   │   │   └── lib.rs       # Public API re-exports
│   │   ├── tests/           # 14 test files, 214+ tests
│   │   └── benches/         # divan benchmarks
│   ├── zapcode-js/         # napi-rs bindings → @unchartedfr/zapcode npm package
│   ├── zapcode-py/         # PyO3 bindings → zapcode pip package
│   └── zapcode-wasm/       # wasm-bindgen target for browser/edge use
├── AGENTS.md                # This file
├── CLAUDE.md                # Claude Code-specific guidance (references this file)
├── Cargo.toml               # Workspace root
└── README.md                # User-facing docs with benchmarks

Read the full file on GitHub · 254 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 · 254 lines · 2,481 tokens per session scan A 340bf17853e2

Subscribe to this mod's changes

zapcode AGENTS.md is an instructions file published in the GitHub repository TheUncharted/zapcode (89 stars, last pushed 3d ago), licensed MIT. It adds 2,481 tokens to every session, about $0.0124 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.