agentmods.dev

seeds: Instructions file for Codex

AGENTS.md

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

Project-specific instructions for AI coding agents working on Seeds, a Git-based issue tracker whose data is stored in text files. They describe the project, tools, layout, and commands.

In plain words
What is it for?
Use them when working on Seeds to find the right files, understand its Bun-based setup, and run the expected commands safely.
Why use it?
They give an agent the key project context and working rules at the start of a session, reducing guesswork about how to build, test, and change the code.

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

not rated 132repo changed 25d ago A scan 2,835 tokens original MIT
View source ↗ jayminwest/seeds
Reuse

Borrowing it

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

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

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

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

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

Security

Grade A, and why

seeds 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 · 252 lines

How it starts

The opening of the file, as written. The whole thing — 252 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 seeds repo, following the agents.md convention. It is intentionally short and command-focused: read it at session start to know how to build, test, and ship. CLAUDE.md is the long-form authoritative companion — when the two disagree, CLAUDE.md wins and this file should be updated to match.

What this project is

Seeds is a git-native issue tracker for AI agent workflows. The JSONL file IS the database: there is no binary store, no export pipeline, no separate sync daemon. All issues live in .seeds/issues.jsonl (one JSON object per line), templates in .seeds/templates.jsonl, plans in .seeds/plans.jsonl, and project config in .seeds/config.yaml. Files are diffable, mergeable (merge=union gitattribute + dedup-on-read), and edited only through the sd CLI, which holds advisory file locks so parallel agents never corrupt the store.

Seeds is part of the os-eco ecosystem alongside warren (control plane), burrow (sandbox), plot (coordination), mulch (expertise), and canopy (prompts). See SPEC.md for the V1 design record.

Tech stack at a glance

  • Runtime: Bun (runs TypeScript directly; no build step).
  • Language: TypeScript, strict mode (noUncheckedIndexedAccess, no any).
  • Lint / format: Biome (biome.json) — tab indentation, 100-char line width, errors fail CI.
  • Tests: bun test, Jest-compatible API, real I/O over temp dirs (no mocks). Tests are *.test.ts co-located with the file under test.
  • Storage: JSONL under .seeds/; minimal built-in YAML parser (src/yaml.ts) for config.
  • CLI: sd, defined in src/index.ts and dispatched via commander.

Project layout

seeds/
├── src/
│   ├── index.ts            # sd CLI entry point + command router
│   ├── version.ts          # VERSION constant (import without CLI side-effects)
│   ├── types.ts            # Issue, Template, Config, shared constants
│   ├── store.ts            # JSONL read/write/lock/atomic-rename
│   ├── id.ts               # ID generation ({project}-{4hex})
│   ├── config.ts           # YAML config load/save
│   ├── output.ts           # JSON + human output helpers
│   ├── yaml.ts             # minimal flat YAML parser
│   └── commands/           # one file per subcommand (create, ready, plan, …)
├── scripts/                # quality-gate scripts + budgets
│   ├── 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
├── .seeds/                 # seeds dogfoods seeds (its own issue store)
├── .factory/skills/        # repo-local agent skills
├── .github/workflows/      # ci.yml + publish.yml + auto-merge.yml
├── CLAUDE.md               # authoritative long-form agent doc
├── RUNBOOK.md              # release / triage / rollback procedures
├── SPEC.md                 # V1 design record
├── README.md               # user-facing pitch
├── CHANGELOG.md            # release history
├── biome.json
├── tsconfig.json
└── package.json

Read the full file on GitHub · 252 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 tokens per session 97eebfde53d4
  2. 1mo ago First seen · 252 lines · 2,833 tokens per session scan A b51b2317037a

Subscribe to this mod's changes

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