elek: Instructions file for Codex

AGENTS.md

elek AGENTS.md is an instructions file for Codex, OpenCode from selimozten/elek. It costs 640 tokens per session, scanned A, original, MIT.

Instructions for elek, a GitHub Action that runs AI code reviews on pull requests and issues. It explains how the TypeScript orchestrator receives GitHub events, gathers change data, and posts review comments.

In plain words
What is it for?
Use it when developing, testing, or changing the GitHub Action and its event-processing or comment-posting workflow.
Why use it?
It gives coding agents the project rules and preserves the review tool's limits, including that it cannot approve, merge, or close pull requests.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/selimozten/elek/agents-md"><img src="https://agentmods.dev/badge/instructions/selimozten/elek/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 640 This file is loaded in full into every session.
When invoked 640 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.00640 $0.00640
Opus 5.5 $0.00256 $0.00256
Sonnet 5.5 $0.00128 $0.00128
Haiku 4.5 $0.00064 $0.00064

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

Security

Grade A, and why

elek 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 14d 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 · 57 lines

How it starts

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

AGENTS.md

Instructions for coding agents working in this repository.

Runtime and boundaries

Elek is a self-hosted composite GitHub Action that wraps the Pi CLI. Read src/entrypoints/run.ts before changing the review flow. On a non-draft pull_request event, one model session reviews the diff with the built-in risk and design lenses. The host sanitizes the final answer and posts GitHub comments through Octokit. There is no hosted service.

Pi gets only its native read, grep, find, and ls tools. src/pi-workspace-guard.ts blocks paths outside the repository, .git, secret files, and symlink escapes. Pi receives no GITHUB_TOKEN. Keep these boundaries intact.

Pi has a built-in MCP client. Elek runs with --no-mcp because the host owns GitHub delivery. Keep MCP adapters, servers, and generated configuration out of the review flow. There must be no review code path to approving, merging, or closing a pull request. Discuss any expansion of that boundary first.

Keep the Action small. New inputs, triggers, or modes need a concrete user problem that the existing inputs and .elek.yml cannot solve.

Implementation

  • Use strict TypeScript. Keep the deliberately loose Octokit adapter types in comments.ts and post-buffered.ts; the full Octokit generic types do not fit their injected dependency interfaces.
  • Add a failing regression test before changing behavior. Prefer pure functions with injected dependencies; see test/post-buffered.test.ts.
  • Keep changes focused. Use Pi's provider support rather than importing model-specific SDKs. Comments explain non-obvious constraints and choices.
  • Close Pi stdin with stdio:["ignore","pipe","pipe"]; an open pipe can leave a noninteractive CLI waiting for input.
  • Await the final progress update before publishing the review so it cannot overwrite the final comment.
  • Pi requires a model with --provider. An empty provider-qualified pattern such as deepseek/ selects an available model within that provider.
  • Keep package-lock.json synchronized with package.json. The Action uses npm ci --omit=dev; CI installs and audits the same lockfile on Node 24.

Read the full file on GitHub · 57 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. 14d ago Changed · +1 lines · +20 tokens per session 15914a242b25
  2. 20d ago Changed · -120 lines · -1,367 tokens per session scan B → A dbbdfd044348
  3. 2mo ago First seen · 176 lines · 1,987 tokens per session scan B 822432582d17

Subscribe to this mod's changes

elek AGENTS.md is an instructions file published in the GitHub repository selimozten/elek (19 stars, last pushed 11d ago), licensed MIT. It adds 640 tokens to every session, about $0.0026 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,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