What is zed-101-setup AGENTS.md?

A set of repository instructions for a Zed Editor configuration bundle. The project stores Zed settings, keyboard shortcuts, and tasks as source files, then uses a command-line script to regenerate the README from them.

It helps edit Zed configuration files, run linting and type checks, regenerate the README, and install the settings into a user's live Zed setup.

It tells coding agents which files are authoritative and how the documentation is generated. This prevents manual README edits from being overwritten or configuration changes from being left undocumented.

How jellydn/zed-101-setup configures Codex and OpenCode

About the project

zed-101-setup is a configuration guide and set of files for preparing the Zed code editor with Vim mode, custom settings, key bindings, local AI assistance, and related terminal and file-search tools. It is for developers who want to configure Zed and safely replace or restore its settings, keymap, and task files. The catalogue entry provides the setup instruction.

jellydn/zed-101-setup · 1,464 stars · on GitHub · itman.fyi

Reuse

Borrowing it

Nothing to install: this file belongs to jellydn/zed-101-setup. 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/jellydn/zed-101-setup/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/jellydn/zed-101-setup

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/jellydn/zed-101-setup/agents-md/github.svg)](https://agentmods.dev/instructions/jellydn/zed-101-setup/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/jellydn/zed-101-setup/agents-md"><img src="https://agentmods.dev/badge/instructions/jellydn/zed-101-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/jellydn/zed-101-setup/agents-md"><img src="https://agentmods.dev/badge/instructions/jellydn/zed-101-setup/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Model	Per session	Once invoked
Fable 5.1	$0.00584	$0.00584
Opus 5.5	$0.00234	$0.00234
Sonnet 5.5	$0.00117	$0.00117
Haiku 4.5	$0.00058	$0.00058

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

Security

Grade A, and why

zed-101-setup 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 2mo 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 · 51 lines

How it starts

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

AGENTS.md

Repo overview

This repo is a Zed Editor configuration bundle — settings.json, keymap.json, tasks.json are the source files. README.md embeds them inside comment markers. cli.ts reads the source files and rewrites the README.

Developer commands

bun run lint          # biome check .
bun run lint:fix      # biome check --write .
bun run typecheck     # tsc --noEmit
bun run start         # bun run cli.ts  (regenerates README.md)
bun run dev           # bun run --hot cli.ts  (hot-reload)

To install configs into your live Zed setup:

sh install.sh         # backs up ~/.config/zed/, copies repo files there

README generation

cli.ts replaces , , and  markers in README.md with the current content of settings.json, keymap.json, and tasks.json. After writing, it runs prettier --write on README.md (falls back to npx prettier, warns if neither is available).

To regenerate from your live Zed config:

sh cli.sh             # copies from ~/.config/zed/, then runs bun run start

Do not manually edit README sections between the comment markers — they are overwritten by cli.ts. Edit settings.json, keymap.json, or tasks.json directly instead.

JSONC caveat

settings.json and keymap.json are JSONC (JSON with Comments), not valid JSON. Biome handles them (json.parser.allowComments: true), but standard JSON linters will choke. They are listed in .gitignore for this reason, yet still tracked in git — don't be confused by the gitignore entry.

Pre-commit & CI

Prettier handles html, css, markdown files.
Biome handles everything else (format, imports, lint, safe fixes).
CI (.github/workflows/pre-commit.yml) runs pre-commit on PRs and pushes to main, then auto-commits any formatting fixes via stefanzweifel/git-auto-commit-action@v7.

Style notes

TypeScript: strict mode, verbatimModuleSyntax, noEmit, ESNext target/module.
Bun runtime — lockfile is bun.lockb.
Biome is the linter/formatter; ESLint is only in example/.
Renovate automerges non-major deps and pins all except peer dependencies.

Read the full file on GitHub · 51 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.

2mo ago First seen · 51 lines · 584 tokens per session scan A a60e32ff9431

Subscribe to this mod's changes

zed-101-setup AGENTS.md is an instructions file published in the GitHub repository jellydn/zed-101-setup (1,464 stars, last pushed yesterday), licensed MIT. It adds 584 tokens to every session, about $0.0023 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.

guide hacktoberfest zed

zed-101-setup AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
zed-101-setup AGENTS.mdjellydn/zed-101-setup	Instructions file	1.5k	yesterday	MIT	A	584	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

zed-101-setup: Instructions file for Codex