mulch: Instructions file for Codex

AGENTS.md

mulch AGENTS.md is an instructions file for Codex, OpenCode from jayminwest/mulch. It costs 2,678 tokens per session, scanned A, original, MIT.

Project instructions for Mulch, a Bun-based command-line tool that stores and retrieves structured expertise for coding agents. JSONL files act as its database, and the tool loads relevant notes into an agent’s context.

In plain words
What is it for?
They help develop and maintain the TypeScript command line, its storage and retrieval flow, and its place in the wider os-eco toolset.
Why use it?
They explain the project’s purpose and conventions so an agent can change the right files and use its commands correctly.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jayminwest/mulch/agents-md"><img src="https://agentmods.dev/badge/instructions/jayminwest/mulch/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,678 This file is loaded in full into every session.
When invoked 2,678 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.02678 $0.02678
Opus 5.5 $0.01071 $0.01071
Sonnet 5.5 $0.00536 $0.00536
Haiku 4.5 $0.00268 $0.00268

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

Security

Grade A, and why

mulch 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 1mo 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 · 225 lines

How it starts

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

AGENTS.md

This file is the canonical entry point for AI coding agents working in the mulch repo, following the agents.md convention. It mirrors the essentials from CLAUDE.md; when the two disagree, CLAUDE.md is authoritative and this file should be updated to match.

What this project is

Mulch is a passive CLI (@os-eco/mulch-cli) that manages structured expertise files for coding agents. It has no LLM dependency — agents call ml record to store an insight and ml prime to load relevant expertise back into context, and mulch handles storage, validation, and retrieval. The JSONL files on disk are the database; ml prime renders them as agent-optimized markdown. Bun is the runtime: the source .ts files execute directly with no build step.

Mulch is part of the os-eco ecosystem alongside warren (control plane), burrow (sandbox), plot (coordination), seeds (issue tracking), and canopy (prompt management). See CLAUDE.md for the long-form design notes and ROADMAP.md for direction.

Tech stack at a glance

  • Runtime: Bun (runs TypeScript directly; no build step on the CLI).
  • Language: TypeScript with strict mode — no any, no @ts-ignore, no @ts-expect-error.
  • Lint / format: Biome (biome.json). Errors fail CI; warnings are promoted to errors via --error-on-warnings.
  • Tests: bun test discovers *.test.ts under test/ and next to scripts; configuration lives in bunfig.toml.
  • Storage: JSONL files under .mulch/expertise/ (one file per domain, append-only, merge=union gitattribute for conflict-free concurrent writes).
  • CLI: ml / mulch (entry point src/cli.ts, dispatched via commander).

Project layout

mulch/
├── src/
│   ├── cli.ts              # ml / mulch CLI entry point + Commander wiring + VERSION
│   ├── index.ts            # library entry point
│   ├── api.ts              # programmatic API surface
│   ├── commands/           # one file per subcommand (record, prime, sync, ...)
│   ├── schemas/            # record schemas + JSON schema definitions
│   ├── registry/           # type registry (built-in + custom types)
│   └── utils/              # lock, expertise IO, git/worktree, runtime flags
├── scripts/                # quality-gate + report scripts and their budgets
│   ├── check-all.ts            # canonical quiet gate runner (byte-identical fleet-wide)
│   ├── check-ci-parity.ts      # CI <-> check:all parity detector (byte-identical fleet-wide)
│   ├── ci-parity-config.json   # per-repo parity escape hatches (aliases / ciOnly)
│   ├── validate-agents-md.ts   # validates this file's references
│   ├── check-file-sizes.ts
│   ├── check-debt-markers.ts
│   ├── check-coverage.ts
│   ├── report-test-timing.ts
│   ├── report-quality-metrics.ts
│   └── version-bump.ts
├── test/                   # bun tests mirroring src/ layout
├── .mulch/                 # mulch's own expertise (dogfood)
├── .factory/skills/        # repo-local agent skills
├── .github/workflows/      # ci.yml + publish.yml + auto-merge.yml
├── README.md               # user-facing pitch
├── CHANGELOG.md            # release history
├── RUNBOOK.md              # release / triage / rollback procedures
├── CONFIG.md               # mulch.config.yaml reference
├── ROADMAP.md              # direction
├── biome.json
├── bunfig.toml
├── tsconfig.json
└── package.json

Read the full file on GitHub · 225 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. 1mo ago First seen · 225 lines · 2,678 tokens per session scan A db5897db31ea

Subscribe to this mod's changes

mulch AGENTS.md is an instructions file published in the GitHub repository jayminwest/mulch (337 stars, last pushed 25d ago), licensed MIT. It adds 2,678 tokens to every session, about $0.0107 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,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,581 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