zuke: Instructions file for Codex

AGENTS.md

zuke AGENTS.md is an instructions file for Codex, OpenCode from zuke-build/zuke. It costs 10,346 tokens per session, scanned A, original, MIT.

Repository instructions for Zuke, a strongly typed build-automation system for Deno and TypeScript. They explain how to find and use Zuke’s published command wrappers without guessing their APIs.

In plain words
What is it for?
Use them when developing zuke-build/zuke or wiring Zuke into another project, especially when selecting packages and checking exact command signatures.
Why use it?
They reduce the risk of using unsupported commands or raw shell calls when automating tasks in a Zuke project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions CLAUDE.md; mentions Claude Code.

This is zuke-build/zuke's own configuration. It tells Codex and OpenCode how to work on zuke itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything zuke configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zuke-build/zuke. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zuke-build/zuke/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/zuke-build/zuke

Made for: Codex, OpenCode.

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

agentmods badge for zuke AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/zuke-build/zuke/agents-md/github.svg)](https://agentmods.dev/instructions/zuke-build/zuke/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/zuke-build/zuke/agents-md"><img src="https://agentmods.dev/badge/instructions/zuke-build/zuke/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for zuke AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zuke-build/zuke/agents-md"><img src="https://agentmods.dev/badge/instructions/zuke-build/zuke/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10,346 This file is loaded in full into every session.
When invoked 10,346 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.10346 $0.10346
Opus 5.5 $0.04138 $0.04138
Sonnet 5.5 $0.02069 $0.02069
Haiku 4.5 $0.01035 $0.01035

Measured 4d ago against content hash af64fda6d2e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zuke 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 4d 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 · 640 lines

How it starts

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

AGENTS.md

Guidance for working in this repository. Read this before making changes.

Zuke is a code-first, strongly-typed build automation system for Deno/TypeScript.

This file, AGENTS.md, is the single source of truth for both humans and agents. CLAUDE.md is a thin pointer whose entire content is @AGENTS.md, so Claude Code loads this file and there is exactly one copy to maintain.

Using Zuke — the API, without guessing

If you are wiring Zuke into a project, do not guess the API and do not fall back to Deno.Command/shell. Every operation has a typed wrapper, and the exact signatures are published — read them:

  • Check the package catalogue before writing any command. llms.txt's ## Packages catalogue (raw: https://raw.githubusercontent.com/zuke-build/zuke/master/llms.txt) and the grouped table in skills/zuke-write-build/references/cheatsheet.md are the only ways to answer "does a @zuke/<tool> wrapper exist for this CLI?" — per-package deno doc jsr:@zuke/<package> can only describe a package whose name you already know; it cannot reveal that a package exists. Reaching for CmdTasks.exec (jsr:@zuke/cmd) or a raw $/Deno.Command for a tool that has a @zuke/<tool> package is a bug, not a style choice — it discards typed flags, argv purity, and tool resolution.
  • One file with the whole typed surface of every package: llms-full.txt at the repo root. llms.txt is the short index.
  • A single wrapper on the command line: deno doc jsr:@zuke/<package> (e.g. deno doc jsr:@zuke/deno).
  • On each package's JSR page / README: a generated ## API section.
  • The CLI surface — commands, flags, and a build's actual targets: run ./zuke --help (or deno run -A zuke.ts --help). It prints the usage grammar, every reserved command (graph, generate-ci, completions <print|install> <shell>, mcp, resume, runs, cancel, register, doc) and flag, plus the current build's targets — with descriptions and dependencies — and its parameters. So an agent asked to set up or run a build discovers the real command surface live instead of guessing; zuke --list is the targets-only view and zuke --list --json emits the whole surface (commands, flags, targets, parameters) as JSON for tools. The written reference is docs/cli.md, and llms.txt carries a generated ## CLI section; the same data is available in code via the exported describeCli(build).

Read the full file on GitHub · 640 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. 4d ago Changed · +16 lines · +309 tokens per session af64fda6d2e4
  2. 9d ago Changed · +3 tokens per session 8e9d4f54854c
  3. 11d ago Changed · +13 lines · +236 tokens per session 59be92af9c88
  4. 14d ago Changed 9bd8ed47eadb
  5. 22d ago Changed 0221e2192959
  6. 25d ago Changed · +10 lines · +214 tokens per session acef535fb228
  7. 1mo ago Changed · +1 lines · +21 tokens per session b30f69c1d9e8
  8. 1mo ago Changed · +8 lines · +154 tokens per session 8b0fcf3bdeb5
  9. 1mo ago Changed · +2 lines · +40 tokens per session d987f281b913
  10. 1mo ago First seen · 590 lines · 9,369 tokens per session scan A 002e843aefae

Subscribe to this mod's changes

zuke AGENTS.md is an instructions file published in the GitHub repository zuke-build/zuke (46 stars, last pushed 2d ago), licensed MIT. It adds 10,346 tokens to every session, about $0.0414 per session on Opus 5.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

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 · 9,649 tokens

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.

vercel/next.js · 7,257 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens