codex-mobile AGENTS.md

A project instruction file for Codex Mobile that defines safe Git workflows for branches, worktrees, rebases, merges, and pull requests.

In plain words
What is it for?
Use it before merging, rebasing, synchronizing branches, continuing interrupted work, or reviewing a pull request's state.
Why use it?
It helps prevent lost changes, stale branch information, and unsafe conflict resolution during collaborative development.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/friuns2/codex-mobile/agents-md
Clone the repo
git clone --depth 1 https://github.com/friuns2/codex-mobile

Made for: Codex, OpenCode.

Per session 2,689 This file is loaded in full into every session.
When invoked 2,689 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.02689 $0.02689
Opus 5 $0.01345 $0.01345
Sonnet 5 $0.00538 $0.00538
Haiku 4.5 $0.00269 $0.00269

Measured 2d ago against content hash 27481dbc0164, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codex-mobile 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 2d 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 · 119 lines

How it starts

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

AGENTS.md

Git Workflow

  • Before any merge, rebase, sync, or continuation after interruption, re-check live state:
    • feature worktree: git status --short, git branch --show-current
    • main worktree: git status --short
    • in-progress state: git status, .git/MERGE_HEAD, .git/rebase-merge, .git/rebase-apply
    • remote/PR state: git fetch origin; when a PR may exist, gh pr view --json number,state,mergeStateStatus,isDraft,headRefName,baseRefName,url
    • branch delta: git diff --stat main...HEAD and git log --oneline main..HEAD
  • Keep both worktrees clean before merge/rebase. Checkpoint local changes in main with git add -A && git commit -m "temp-before-merge-<branch>"; skip only if main is clean.
  • Prefer GitHub PR update/rebase/merge when a PR or GitHub merge path exists. Use local main merge only when no PR/GitHub path exists or the user explicitly asks for a local merge.
  • Standard path: commit task, create/switch feature branch, rebase on main, then use the chosen PR/local merge path.
  • Never use automatic conflict-bias strategies blindly (-X theirs, -X ours, git checkout --theirs ., git checkout --ours .). Inspect conflicts intentionally.
  • Avoid rebasing long-lived mixed-history branches if it pulls broad unrelated conflicts. Abort and use a fresh branch from main plus task-relevant cherry-picks.
  • If package.json, tests.md, or files under tests/ conflict during merge/rebase, start from the local/checkpoint version, then explicitly compare incoming changes and reconcile required updates before continuing.
  • Before local main merge, diff-compare all branch changes against main.
  • After merge/sync, verify the target really contains the commit with git branch --contains <commit>, git log --oneline origin/main -10, or a file-level diff against origin/main.

Commits

  • Commit after each discrete task or sub-task.
  • Do not batch unrelated tasks into one commit.
  • Use a specific commit message describing the change.

Read the full file on GitHub · 119 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. 2d ago First seen · 119 lines · 2,689 tokens per session scan A 27481dbc0164

Subscribe to this mod's changes

codex-mobile AGENTS.md is an instructions file published in the GitHub repository friuns2/codex-mobile (893 stars, last pushed 3mo ago), licensed MIT. It adds 2,689 tokens to every session, about $0.0134 per session on Opus 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.