agentmods.dev

openclaw-termux: Instructions file for Codex

AGENTS.md

openclaw-termux AGENTS.md is an instructions file for Codex, OpenCode from yunze7373/openclaw-termux. It costs 6,245 tokens per session, scanned D, a copy of openclaw-cn AGENTS.md, MIT.

Repository instructions for working on OpenClaw, an open-source project with messaging, media, web-provider, and infrastructure code.

In plain words
What is it for?
Use them when modifying OpenClaw source code, tests, Mintlify documentation, Chinese translations, or related development workflows.
Why use it?
They explain the project’s layout and rules for writing documentation, GitHub comments, security reviews, and code changes.

Instructions file for CodexOpenCode

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

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

not rated 2repo 2mo ago D scan 6,245 tokens copy · 94% MIT
View source ↗ yunze7373/openclaw-termux
Reuse

Borrowing it

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

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 openclaw-termux AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yunze7373/openclaw-termux/agents-md.svg)](https://agentmods.dev/instructions/yunze7373/openclaw-termux/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/yunze7373/openclaw-termux/agents-md"><img src="https://agentmods.dev/badge/instructions/yunze7373/openclaw-termux/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 6,245 This file is loaded in full into every session.
When invoked 6,245 The same file — it is already loaded in full.
Security scan D 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod 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.06245 $0.06245
Opus 5 $0.03122 $0.03122
Sonnet 5 $0.01249 $0.01249
Haiku 4.5 $0.00624 $0.00624

Measured 8d ago against content hash 9fed1a0a6bec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade D, and why

openclaw-termux AGENTS.md scanned grade D with 2 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 8d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Update: `sudo npm i -g openclaw@latest` (global install needs root on `/usr/lib/node_modules`).

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- **Build on-device**: never copy `dist/` from Windows/macOS to Termux; rebuild on the Termux device (`rm -rf dist && pnpm install && pnpm build`).
Origin

This is a copy

94% identical to openclaw-cn AGENTS.md — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 267 lines

How it starts

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

Repository Guidelines

  • Repo: https://github.com/openclaw/openclaw
  • In chat replies, file references must be repo-root relative only (example: extensions/bluebubbles/src/channel.ts:80); never absolute paths or ~/....
  • GitHub issues/comments/PR comments: use literal multiline strings or -F - <<'EOF' (or $'...') for real newlines; never embed "\n".
  • GitHub comment footgun: never use gh issue/pr comment -b "..." when body contains backticks or shell chars. Always use single-quoted heredoc (-F - <<'EOF') so no command substitution/escaping corruption.
  • GitHub linking footgun: don’t wrap issue/PR refs like #24643 in backticks when you want auto-linking. Use plain #24643 (optionally add full URL).
  • Security advisory analysis: before triage/severity decisions, read SECURITY.md to align with OpenClaw's trust model and design boundaries.

Project Structure & Module Organization

  • Source code: src/ (CLI wiring in src/cli, commands in src/commands, web provider in src/provider-web.ts, infra in src/infra, media pipeline in src/media).
  • Tests: colocated *.test.ts.
  • Docs: docs/ (images, queue, Pi config). Built output lives in dist/.
  • Plugins/extensions: live under extensions/* (workspace packages). Keep plugin-only deps in the extension package.json; do not add them to the root package.json unless core uses them.
  • Plugins: install runs npm install --omit=dev in plugin dir; runtime deps must live in dependencies. Avoid workspace:* in dependencies (npm install breaks); put openclaw in devDependencies or peerDependencies instead (runtime resolves openclaw/plugin-sdk via jiti alias).
  • Installers served from https://openclaw.ai/*: live in the sibling repo ../openclaw.ai (public/install.sh, public/install-cli.sh, public/install.ps1).
  • Messaging channels: always consider all built-in + extension channels when refactoring shared logic (routing, allowlists, pairing, command gating, onboarding, docs).
    • Core channel docs: docs/channels/
    • Core channel code: src/telegram, src/discord, src/slack, src/signal, src/imessage, src/web (WhatsApp web), src/channels, src/routing
    • Extensions (channel plugins): extensions/* (e.g. extensions/msteams, extensions/matrix, extensions/zalo, extensions/zalouser, extensions/voice-call)
  • When adding channels/extensions/apps/docs, update .github/labeler.yml and create matching GitHub labels (use existing channel/extension label colors).

Read the full file on GitHub · 267 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. 8d ago First seen · 267 lines · 6,245 tokens per session scan D 9fed1a0a6bec

Subscribe to this mod's changes

openclaw-termux AGENTS.md is an instructions file published in the GitHub repository yunze7373/openclaw-termux (2 stars, last pushed 2mo ago), licensed MIT. It adds 6,245 tokens to every session, about $0.0312 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). It is 94% identical to openclaw-cn AGENTS.md, differing in 10 lines, and is treated as a copy.

ai-agentsai-assistantandroidautomationdeveloper-toolsedge-ai
Related

Other instructions, from other repositories

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens