ensemblr: Instructions file for Codex

AGENTS.md

ensemblr AGENTS.md is an instructions file for Codex, OpenCode from ensemblr-hq/ensemblr. It costs 3,214 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for Ensemblr, including its naming rules, package-manager policy, and requirement to consult current official documentation when scaffolding software.

In plain words
What is it for?
Scaffolding apps or integrations, choosing installation commands, and keeping names, tooling, and generated files aligned with the repository.
Why use it?
They prevent outdated setup steps and inconsistent references from being used while changing the project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions AGENTS.md; mentions Codex.

This is ensemblr-hq/ensemblr's own configuration. It tells Codex and OpenCode how to work on ensemblr 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 ensemblr configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ensemblr-hq/ensemblr. 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/ensemblr-hq/ensemblr/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ensemblr-hq/ensemblr

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 ensemblr AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ensemblr-hq/ensemblr/agents-md/github.svg)](https://agentmods.dev/instructions/ensemblr-hq/ensemblr/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ensemblr-hq/ensemblr/agents-md"><img src="https://agentmods.dev/badge/instructions/ensemblr-hq/ensemblr/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 ensemblr AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ensemblr-hq/ensemblr/agents-md"><img src="https://agentmods.dev/badge/instructions/ensemblr-hq/ensemblr/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,214 This file is loaded in full into every session.
When invoked 3,214 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.03214 $0.03214
Opus 5.5 $0.01286 $0.01286
Sonnet 5.5 $0.00643 $0.00643
Haiku 4.5 $0.00321 $0.00321

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

Security

Grade A, and why

ensemblr 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 25d 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 · 126 lines

How it starts

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

Agent Instructions

These instructions apply to the whole repository.

Repository Layout

This is a Bun workspaces monorepo.

Path What lives there
apps/desktop/ Ensemblr, the Electron desktop app: its source, tests, scripts, docs, JSON Schemas, assets, Nix packaging, changelog, and release notes.
apps/website/ The marketing and documentation site. Not started yet.
packages/shared/ Code the apps share, such as UI pieces lifted out of the desktop app. Not started yet.

The root holds only what the whole repository shares: the workspace manifest (package.json) and lockfile, the install settings (bunfig.toml; the toolchain itself is the Nix dev shell in flake.nix), the house Biome config, the monorepo-level scripts in scripts/, CI (.github/), agent tooling (.claude/, .codex/, .agents/, .mcp.json), Ensemblr's repository settings (.ensemblr/), the Nix flake entrypoint, and the community files. Keep it that way: anything that belongs to one app or package lives under that workspace's directory.

  • Before working under apps/desktop/, read apps/desktop/AGENTS.md. Its paths, and those in the scoped AGENTS.md files beneath it, are relative to apps/desktop/.
  • When you write a path in prose, write it from the repository root, workspace prefix included — apps/desktop/src/main/main.ts, not src/main/main.ts.

Workspaces

  • The root package.json workspaces globs apps/* and packages/*; a directory becomes a workspace when it gets a package.json. Name a new package @ensemblr/<name>, mark it private, and depend on another workspace with "workspace:*". The desktop app keeps the package name ensemblr, which its Electron identity and release tooling read.
  • Bun runs a workspace's own preinstall and postinstall only when it first installs that workspace — not when a dependency changes, and not on an install with nothing to do. The root manifest's preinstall and postinstall therefore run every workspace's (bun run --workspaces --if-present) on every install, the way a single-package root's ran before; on a first install they run twice, so keep them idempotent.
  • Each workspace owns its check, typecheck, and test scripts. The root's scripts of the same name run every workspace's (bun run --workspaces --if-present <script>); check first runs the lockfile check and Biome over the whole tree (each file under its nearest biome.json).
  • Install from anywhere with bun install or bun ci; Bun installs every workspace and hoists dependencies into the root node_modules. Add a dependency to the workspace that uses it (bun add <pkg> inside that workspace's directory, or bun add <pkg> --cwd apps/desktop), never to the root manifest.
  • A new workspace manifest changes what bun install lays out, so it moves the Nix deps hash: re-pin with apps/desktop/nix/update-pins.sh deps (the nix-deps check reports the new hash on a pull request).

Read the full file on GitHub · 126 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. 25d ago Changed · +2 lines · +118 tokens per session 5fa8d813868c
  2. 26d ago Changed · -39 lines · -1,684 tokens per session 66119cdc314f
  3. 28d ago Changed · +71 tokens per session c25aa16594cc
  4. 1mo ago Changed · +5 lines · +538 tokens per session bc119efc71be
  5. 1mo ago Changed · +40 tokens per session 94a6be94afe1
  6. 1mo ago First seen · 158 lines · 4,131 tokens per session scan A 11cf4292bb56

Subscribe to this mod's changes

ensemblr AGENTS.md is an instructions file published in the GitHub repository ensemblr-hq/ensemblr (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,214 tokens to every session, about $0.0129 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-31.

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,715 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,461 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

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

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,261 tokens