garden-desk: Instructions file for Codex

AGENTS.md

garden-desk AGENTS.md is an instructions file for Codex, OpenCode from alex-alecu/garden-desk. It costs 2,445 tokens per session, scanned A, original, Apache-2.0.

A repository instruction file that sets the current development phase and working rules for garden-desk, an offline developer-agent desktop project.

In plain words
What is it for?
Implementing approved M3 work, checking the current project status, preserving earlier contracts and security components, and testing boundaries and recovery behavior.
Why use it?
It prevents the agent from starting out-of-scope future work and defines which tests and completed systems must be preserved.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 garden-desk AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/alex-alecu/garden-desk/agents-md"><img src="https://agentmods.dev/badge/instructions/alex-alecu/garden-desk/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,445 This file is loaded in full into every session.
When invoked 2,445 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.02445 $0.02445
Opus 5 $0.01222 $0.01222
Sonnet 5 $0.00489 $0.00489
Haiku 4.5 $0.00245 $0.00245

Measured yesterday against content hash b362053ab740, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

garden-desk 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 yesterday.

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 · 89 lines

How it starts

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

AGENTS.md

This file is the control document for agents working in this repository. It is authoritative, followed by accepted ADRs, docs/IMPLEMENTATION_PLAN.md, and docs/DEVELOPMENT_WORKFLOW.md.

Top Priority: Minimum Work

This rule applies to Codex and all other agents. It controls all later repository documents, skills, and general completion rules. Only an explicit owner request can increase the work or verification scope.

  • Make the smallest correct change for the requested outcome. Keep required security, privacy, authority, and active product contracts complete.
  • Do not add adjacent refactors, speculative abstractions, defensive branches, options, fallbacks, compatibility layers, documentation, or cleanup.
  • Default to zero new tests. A bug gets one reproducing test. A new boundary or business rule gets at most one focused test.
  • Run only the smallest check that proves the changed behavior. Do not run the full unit suite, repository gate, milestone gate, real model, or physical microVM only for more confidence.
  • A general skill, completion checklist, review request, commit, push, or pull request does not increase the scope. If a later instruction conflicts with this rule, use the smaller change and smaller verification set.
  • Ask the owner before you add scope, tests, or verification beyond this rule.

A real run is any command or script that loads a real model or starts a physical microVM. This includes a focused real-model reproduction, pnpm test:m3:macos, pnpm test:m3:windows, pnpm test:gate --milestone 3, and wrappers that start them. First use source inspection, existing evidence, and focused deterministic tests. If a real run is still necessary, state the unresolved question, why cheaper evidence cannot answer it, the exact command or workload, and the number of planned invocations. Then ask the owner. A direct owner request for that workload is approval. Approval covers only the named commands and invocation count. A retry needs new approval.

Read the full file on GitHub · 89 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. yesterday Changed · +13 tokens per session b362053ab740
  2. 5d ago Changed · +13 lines · +376 tokens per session e89bcbd481c9
  3. 9d ago First seen · 76 lines · 2,056 tokens per session scan A 99ca2e2e74a5

Subscribe to this mod's changes

garden-desk AGENTS.md is an instructions file published in the GitHub repository alex-alecu/garden-desk (6 stars, last pushed today), licensed Apache-2.0. It adds 2,445 tokens to every session, about $0.0122 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-31.

Related

Other instructions, from other repositories

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

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 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 · 3,735 tokens