Home / kamioj / spec-workflow · GitHub

AGENTS.md@codexA

AGENTS.md@codex from kamioj/spec-workflow is an AGENTS.md file: the standing instructions coding agents read in that repo.

Install it, pinned

mdr add kamioj/spec-workflow/codex/AGENTS.md@git:20260714.2d7154d

Pins git:20260714.2d7154d in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 14 of 14 checks passed
Kind: AGENTS.md file
Repository: kamioj/spec-workflow
Path: codex/AGENTS.md
Versions recorded: 2
Latest version: git:20260714.2d7154d, committed Jul 14, 2026
First version recorded: Jul 9, 2026
Size: 1,897 bytes
Repository stars: 20
License: a license file GitHub does not identify

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# SDD workflow (Codex CLI)

This project uses the sdd spec-driven development workflow. Large changes (>150 lines /
3+ files / new dependency / architecture choice) go through the gated flow instead of
being implemented directly:

```
$spec-research → $spec-ask → ($spec-design) → $spec-propose → [HARD GATE] → $spec-apply → $spec-verify → $spec-archive
```

Rules that bind you, the agent:

- **Never write project source before the HARD GATE is approved.** After emitting the
  `<HARD-GATE>` block at the end of `$spec-propose`, stop and wait for the user. The
  `<!-- APPROVED: ... -->` marker is appended by `$spec-apply` itself — do not add it,
  and never add it on the user's behalf.
- **Artifacts are fixed**: `spec/changes/<name>/` holds research.md, design.md (optional),
  proposal.md, tasks.md (optional), verify.md; project-durable facts go to
  `spec/knowledge.md`. Inventing extra artifact files requires explicit user approval.
- **Verification is independent**: `$spec-verify` spawns the spec-verifier agent
  (`~/.codex/agents/spec-verifier.toml`) with a fresh context. The conversation that
  implemented a change never audits itself.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kamioj/spec-workflow/codex/AGENTS.md@sha256:c9dd3f559ac1e329

The line at the top of this page pins the label git:20260714.2d7154d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_7jywtq66hzzybb66.svg)](https://markdownregistry.com/a/art_7jywtq66hzzybb66)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Jul 9, 2026 and Jul 14, 2026, about one every 5 days.

version	committed	commit	size	audit
git:20260714.2d7154d latest	2026-07-14	2d7154d	1,897 B	A	view · diff
git:20260709.322dd02	2026-07-09	322dd02	1,716 B	A	view

Audit of the latest version

A 14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Size between 200 bytes and 200 KB (1897 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

kamioj/spec-workflow · 20 stars · license a license file GitHub does not identify · pushed 2026-09-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_7jywtq66hzzybb66
GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/codex/AGENTS.md
GET https://markdownregistry.com/api/v1/blob/c9dd3f559ac1e329462195f640a644665b71ae7c488a60ca7d7bde0afdf3688e

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.