open-computer-use AGENTS.md

Repository instructions for the open-computer-use project, a system for letting AI agents operate computers. They point agents to the project’s architecture, collaboration, quality, security, and other documentation.

In plain words
What is it for?
Use them when working on open-computer-use, especially before starting tasks, editing code, updating documents, or preparing changes for review.
Why use it?
They help agents follow the repository’s rules and read the right guidance before changing code or workflows.

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/opensymph/open-computer-use/agents-md
Clone the repo
git clone --depth 1 https://github.com/opensymph/open-computer-use

Made for: Codex, OpenCode.

Per session 589 This file is loaded in full into every session.
When invoked 589 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.00589 $0.00589
Opus 5 $0.00295 $0.00295
Sonnet 5 $0.00118 $0.00118
Haiku 4.5 $0.00059 $0.00059

Measured yesterday against content hash cfc44d2be23d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

open-computer-use 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 yesterday.

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 · 40 lines

What it actually says

open-computer-use

这个仓库是一个面向 Agent 协作开发的 Computer Use 项目。

AGENTS.md 故意保持简短,只负责做导航,不负责塞满所有规则。仓库内的 docs/ 才是本地知识的正式来源。

如果一次代码或流程变更会让某份文档过期,就在同一轮任务里顺手把它改掉。

每轮开始先读

  • docs/REPO_COLLAB_GUIDE.md:仓库级协作、提交、文档同步与测试约定。
  • docs/ARCHITECTURE.md:仓库整体结构和预期边界。
  • docs/design-docs/core-beliefs.md:Agent-first 的工作原则和这个模板的设计出发点。

代码改完前要读

  • docs/QUALITY_SCORE.md:当前质量分层和主要短板。

按任务需要选读

  • docs/PRODUCT_SENSE.md:产品价值、取舍方式和优先级判断。
  • docs/RELIABILITY.md:运行稳定性、观测性和上线前的基本要求。
  • docs/SECURITY.md:认证、数据处理、外部集成等安全默认约束。
  • docs/SUPPLY_CHAIN_SECURITY.md:依赖、SBOM、制品 provenance 和仓库级供应链安全默认做法。
  • docs/CICD.md:仓库的 CI/CD 骨架以及后续如何接入真实项目。
  • docs/FRONTEND.md:如果仓库包含前端界面,这里记录对应规范。
  • CONTRIBUTING.md:提 PR 前后的默认检查项和协作要求。
  • docs/releases/README.md:如何维护面向用户的发布记录。
  • docs/releases/RELEASE_GUIDE.md:只要任务涉及 bump 版本、打 tag、推 release,先读这份发版必读。
  • docs/references/README.md:沉淀到仓库里的外部参考资料。

工作规则

  • 优先选择小而清晰、对仓库和 Agent 都友好的抽象。
  • 回复默认跟随用户提问所使用的语言;如果用户切换语言,回复语言也随之切换。
  • 如果用户这一轮输入是英文,则直接用英文回复。
  • 推送前先同步远端最新代码,再执行 git push
  • prompt、规则、架构约束尽量都版本化落在仓库里。
  • 跨多轮的复杂任务先写清楚计划再动手,并把关键决策落到文档里。
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. yesterday First seen · 40 lines · 589 tokens per session scan A cfc44d2be23d

Subscribe to this mod's changes

open-computer-use AGENTS.md is an instructions file published in the GitHub repository opensymph/open-computer-use (2 stars, last pushed 6d ago), licensed MIT. It adds 589 tokens to every session, about $0.0029 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-31.

Related

Other instructions, from other repositories

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

buildNext

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

next.js 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

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

spec-kit 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,040 tokens

langchain 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,345 tokens