What is gather-step AGENTS.md?

Project instructions for the gather-step workflow, which helps agents collect and review changes in a code repository. They define conventions for commits, Rust checks, formatting, linting, signing, and pull-request reviews.

Use them when reviewing a pull request with gather-step or preparing changes in this Rust project, including running checks, formatting code, and creating compliant commits.

They give agents consistent project rules to follow and reduce review or submission errors caused by missed checks, incorrect commit messages, or broken signing settings.

How thedoublejay/gather-step configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to thedoublejay/gather-step. 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/thedoublejay/gather-step/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/thedoublejay/gather-step

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/thedoublejay/gather-step/agents-md/github.svg)](https://agentmods.dev/instructions/thedoublejay/gather-step/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/thedoublejay/gather-step/agents-md"><img src="https://agentmods.dev/badge/instructions/thedoublejay/gather-step/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/thedoublejay/gather-step/agents-md"><img src="https://agentmods.dev/badge/instructions/thedoublejay/gather-step/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 905 This file is loaded in full into every session.

When invoked 905 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.

Model	Per session	Once invoked
Fable 5.1	$0.00905	$0.00905
Opus 5.5	$0.00362	$0.00362
Sonnet 5.5	$0.00181	$0.00181
Haiku 4.5	$0.00090	$0.00090

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

Security

Grade A, and why

gather-step 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 2mo 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 · 45 lines

How it starts

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

AGENTS.md — Gather Step

Memory file for Codex / Gather Step agents. Project conventions and the canonical workflows for this codebase.

Conventions

Commit messages: Conventional Commits (feat:, fix:, docs:, refactor:, test:, chore:, etc.). Keep the subject under 72 characters.
No trailers: Never add Co-Authored-By or Signed-off-by to commits.
Signing: Tests must run cleanly with commit.gpgsign = true set globally. Fixture helpers that create git commits must disable signing locally (e.g., git -c commit.gpgsign=false commit ...) so CI and dev environments that have GPG signing enabled do not break.
Lint bar: cargo clippy --workspace --all-targets -- -D warnings must pass clean. No #[allow(clippy::...)] without an #[expect(..., reason = "...")] that explains why.
Formatting: cargo fmt --all before committing. rustfmt.toml is the authority.
Type-check first: Run cargo check --workspace before submitting any change that touches non-trivial Rust.

Reviewing a PR with gather-step

When the user says "review this PR using gather-step" (or any close variant — "review the PR", "do a structural review with gather-step", etc.):

Run gather-step pr-review --base <base> --head <head> --json to build the review index and emit a structured delta report. Use --keep-cache if the user wants to ask follow-up questions against the review index.
Warn the user before the first run that it will take a minute or two: a fresh review index is being built from scratch in a disposable Gather Step storage. Subsequent runs against the same SHAs may reuse the cache.
Read the report's metadata, safety, changed_files, and suggested_followups. The current schema_version (defined by DELTA_REPORT_SCHEMA_VERSION in crates/gather-step-cli/src/pr_review/delta_report.rs) populates routes, symbols, payload_contracts, events, decorators, contract_alignments, removed_surface_risks, and deployment in addition to the metadata surfaces — none of these are stubs.
For deep follow-ups, run the suggested commands as-is. They include --registry / --storage overrides pointing at the kept review index, so they read the PR-branch state, not the workspace baseline.
Only fall back to manual diff inspection if pr-review is unavailable or fails. Never silently skip it for a structured review request.

Read the full file on GitHub · 45 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.

2mo ago First seen · 45 lines · 905 tokens per session scan A 80f06824363d

Subscribe to this mod's changes

gather-step AGENTS.md is an instructions file published in the GitHub repository thedoublejay/gather-step (9 stars, last pushed 3mo ago), licensed MIT. It adds 905 tokens to every session, about $0.0036 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.

ai ai-agents ai-graph

gather-step AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gather-step AGENTS.mdthedoublejay/gather-step	Instructions file	9	3mo ago	MIT	A	905	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

gather-step: Instructions file for Codex