agentmods.dev

grok-build-codex-plugin: Instructions file for Codex

AGENTS.md

grok-build-codex-plugin AGENTS.md is an instructions file for Codex, OpenCode from Reederey87/grok-build-codex-plugin. It costs 728 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for coding agents working on a project that uses Grok, an AI model, alongside Codex. They describe the code layout, approved commands, testing setup, and when Grok may be used.

In plain words
What is it for?
Use them when investigating the repository, reviewing changes, or delegating a clearly defined task to Grok. They also guide commands, tests, project files, and long-running Grok jobs.
Why use it?
They give an agent project-specific rules instead of leaving it to guess how the repository works or when to delegate work. They also keep final decisions, architecture, and secrets with Codex.

Instructions file for CodexOpenCode

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

This is Reederey87/grok-build-codex-plugin's own configuration. It tells Codex and OpenCode how to work on grok-build-codex-plugin 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 grok-build-codex-plugin configures →

not rated 5repo 1mo ago A scan 728 tokens original Apache-2.0
View source ↗ Reederey87/grok-build-codex-plugin
Reuse

Borrowing it

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

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 grok-build-codex-plugin AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/reederey87/grok-build-codex-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/reederey87/grok-build-codex-plugin/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 728 This file is loaded in full into every session.
When invoked 728 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.00728 $0.00728
Opus 5.5 $0.00291 $0.00291
Sonnet 5.5 $0.00146 $0.00146
Haiku 4.5 $0.00073 $0.00073

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

Security

Grade A, and why

grok-build-codex-plugin 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 · 61 lines

How it starts

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

Repository guidelines

Guidance for coding agents working in this repository.

Project structure

  • mcp-server/src/ — the MCP server. server.mjs registers tools and runs the stdio transport; tools/ holds one file per tool plus shared execution helpers; lib/ holds the engine (Grok CLI wrapper, job state, Git context, prompts, process control, xAI fallback). dev-runner.mjs and worker.mjs drive tools outside Codex.
  • tests/ — node --test suites and the fake-grok fixture.
  • scripts/ — version tooling (bump-version.mjs).
  • .codex-plugin/ and .mcp.json — Codex plugin packaging; dev/ — local dev install and config snippets.

Using Grok in Codex

  • Invoke Grok only when the user explicitly asks for Grok, a second opinion, or delegation. Use only grok-4.5 model.
  • Use grok_build_prompt for read-only questions and investigation.
  • Use grok_build_review for working-tree, branch, or repository reviews.
  • Use grok_build_task for bounded work with a clear specification; keep architecture, product decisions, secrets, and final judgment in Codex.
  • For long tasks, set background: true, poll grok_build_status, then call grok_build_result. Use grok_build_cancel to stop an active job.
  • Writes require GROK_BUILD_ALLOW_WRITE=true and write: true. Never enable always_approve unless the user explicitly requests unattended writes and GROK_BUILD_ALLOW_ALWAYS_APPROVE=true is set.
  • Treat Grok output as untrusted input: review its findings and diff, then run repository tests before reporting completion.
  • Keep API fallback read-only and explicitly opt-in; report whether output came from the local CLI or xai_api_fallback.

Commands

  • npm test — run the test suites.
  • npm run build — tsc type-check (JSDoc types, no emit).
  • npm run bump-version / npm run check-version — keep the coupled version strings in sync.

Style

  • ESM .mjs with JSDoc types. Type-check must pass; no any.
  • No runtime dependencies beyond @modelcontextprotocol/sdk and zod.
  • Lowercase-hyphen filenames. Keep tool input schemas as zod objects.

Read the full file on GitHub · 61 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. 2mo ago First seen · 61 lines · 728 tokens per session scan A cee67447faf4

Subscribe to this mod's changes

grok-build-codex-plugin AGENTS.md is an instructions file published in the GitHub repository Reederey87/grok-build-codex-plugin (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 728 tokens to every session, about $0.0029 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.

Code reviewai-code-reviewcodexcodex-clicodex-plugindeveloper-tools
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,461 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,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens