OpenOffice: Instructions file for Claude Code

CLAUDE.md

OpenOffice CLAUDE.md is an instructions file for Claude Code from longyangxi/OpenOffice. It costs 582 tokens per session, scanned A, original, MIT.

A project instruction file that explains the structure, commands, architecture, data locations, Git rules, and isolated workspaces for the Open Office project.

In plain words
What is it for?
Use it when working on the Open Office codebase, including its web app, gateway, shared packages, agent orchestration, memory, and Git workflow.
Why use it?
It gives coding agents the project-specific context they need before changing code. This reduces confusion about where components live and how the project should be run or modified.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is longyangxi/OpenOffice's own configuration. It tells Claude Code how to work on OpenOffice 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 OpenOffice configures →

Reuse

Borrowing it

Nothing to install: this file belongs to longyangxi/OpenOffice. 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/longyangxi/OpenOffice/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/longyangxi/OpenOffice

Made for: Claude Code.

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 OpenOffice CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/longyangxi/openoffice/claude-md/github.svg)](https://agentmods.dev/instructions/longyangxi/openoffice/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/longyangxi/openoffice/claude-md"><img src="https://agentmods.dev/badge/instructions/longyangxi/openoffice/claude-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 OpenOffice CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/longyangxi/openoffice/claude-md"><img src="https://agentmods.dev/badge/instructions/longyangxi/openoffice/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 582 This file is loaded in full into every session.
When invoked 582 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.00582 $0.00582
Opus 5.5 $0.00233 $0.00233
Sonnet 5.5 $0.00116 $0.00116
Haiku 4.5 $0.00058 $0.00058

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

Security

Grade A, and why

OpenOffice CLAUDE.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 1mo 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.

CLAUDE.md · 48 lines

How it starts

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

Open Office

Project Structure

  • apps/web - Next.js 15 PWA (Vercel deployment)
  • apps/gateway - Mac daemon (Node.js + multi-channel + AI CLI control)
  • packages/shared - Shared event protocol (Zod schemas)
  • packages/orchestrator - Multi-agent engine (worktree, delegation, phases)
  • packages/memory - Persistent agent memory (sessions, facts, shared knowledge)

Git

  • All git commit messages MUST be in English.

Key Commands

  • pnpm dev:web - Start web dev server
  • pnpm dev:gateway - Start gateway

Architecture

  • Channels: WebSocket (always), Ably (optional), Telegram (optional)
  • UI: PixiJS v8 pixel office + Key Node Mode agent cards

Data Directory

  • Dev: ~/.open-office-dev/, Release: ~/.open-office/
  • config.json — global config
  • data/instances/<id>/ — per-gateway state (logs, sessions, memory)
  • data/agents.json — agent definitions
  • projects/ — default agent workspace (team projects created here)
  • worktrees/<repo-hash>/<agentId>/ — centralized worktree isolation

Worktree Isolation

  • One agent = one worktree = one branch (keyed by agentId, not taskId)
  • Worktrees stored outside repo at ~/.open-office[-dev]/worktrees/ to prevent path traversal
  • On task:done: auto-merge to main (default), with per-agent toggle + undo merge
  • Before each task: auto-rebase onto latest main, conflicts auto-resolved
  • Cleanup: on fire agent only (no startup GC)
  • Full docs: packages/orchestrator/README.md → "Worktree Isolation"

Key Node Mode

Only 4 key events shown in UI: TASK_STARTED, APPROVAL_NEEDED, TASK_DONE, TASK_FAILED. Agent states: idle, working, waiting_approval, done, error. TASK_DONE includes structured result (changedFiles, diffStat, testResult).

Team Execution Flow

Phases: CREATE → DESIGN → EXECUTE → COMPLETE → (loop or END). Execute: Leader → Dev (build+self-fix) → Reviewer (VERDICT) → Fix loop (max 3 reviews). Roles: Developer (ENTRY_FILE or PREVIEW_CMD+PORT), Code Reviewer (VERDICT PASS/FAIL), Team Lead (delegates only). Preview: static HTML (npx serve:9100), build output (dist/index.html), or command (PREVIEW_CMD on PREVIEW_PORT). Project dir: unique per session, all members share it. Created on APPROVE_PLAN.

Read the full file on GitHub · 48 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. 1mo ago First seen · 48 lines · 582 tokens per session scan A 92943bfb9b26

Subscribe to this mod's changes

OpenOffice CLAUDE.md is an instructions file published in the GitHub repository longyangxi/OpenOffice (268 stars, last pushed 2mo ago), licensed MIT. It adds 582 tokens to every session, about $0.0023 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