maxclaw: Instructions file for Codex

AGENTS.md

maxclaw AGENTS.md is an instructions file for Codex, OpenCode from Lichas/maxclaw. It costs 663 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for Lichas/maxclaw, including the required development workflow, parallel sessions using Git worktrees, and a rule for finding interface icons.

In plain words
What is it for?
Use them when modifying this repository, especially for implementing features, running builds or end-to-end tests, handling UI state, or preparing a commit.
Why use it?
They help coding agents complete changes consistently, run the required checks, update the changelog, and record the work in Git.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lichas/maxclaw/agents-md"><img src="https://agentmods.dev/badge/instructions/lichas/maxclaw/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 663 This file is loaded in full into every session.
When invoked 663 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.00663 $0.00663
Opus 5.5 $0.00265 $0.00265
Sonnet 5.5 $0.00133 $0.00133
Haiku 4.5 $0.00066 $0.00066

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

Security

Grade A, and why

maxclaw 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

This file provides guidance to coding agents (Codex, Claude, and similar) when working in this repository.

Required Workflow

  • Complete the user request end-to-end: implement, verify, then report.
  • Run relevant validation (tests/build/smoke) yourself; do not ask the user to verify in your place.
  • If a request changes repository files, run the relevant E2E/regression test script(s) before finishing. If any E2E test fails, investigate the failure and either fix it or clearly report the blocker; do not ignore the failure.
  • After successfully completing a request that changes repository files, run make build and then create a git commit for that request.
  • If a user request results in a repository change (feature, bug fix, behavior change, config change, or docs change), you must append an entry to CHANGELOG.md under ## [Unreleased].
  • Changelog entries should be concise and include:
    • what changed
    • where (key files)
    • how it was verified (test/build command)
  • If no repository files were changed, explicitly state that no changelog update is needed.
  • When changing stateful UI or session-management logic, think through the full interaction loop before editing:
    • identify every effect, auto-redirect, default selection, and persistence path that can overwrite the new state
    • verify the intended empty/initial state, transition state, and restored state separately
    • avoid "local fix, global regression" changes where one handler is updated but linked sync logic still forces old behavior back
  • Core flows must gain regression coverage when they change:
    • for session creation, chat routing, interrupt/resume, spawn/callback, and other user-visible control flow, add or extend an automated E2E/regression test in e2e_test/
    • do not treat manual clicking as sufficient verification for these paths
    • if full UI automation is not available yet, still add the closest end-to-end regression that exercises the real persistence/API boundary and document the remaining gap

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.

  1. 2mo ago First seen · 45 lines · 663 tokens per session scan A e3b175ba855a

Subscribe to this mod's changes

maxclaw AGENTS.md is an instructions file published in the GitHub repository Lichas/maxclaw (230 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 663 tokens to every session, about $0.0027 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

maxclaw AGENTS.md compared with instructions from other repositories

maxclaw AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
maxclaw AGENTS.mdLichas/maxclawInstructions file2304mo agoApache-2.0A663Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode