Borrowing it
Nothing to install: this file belongs to Maidang1/open-claude-cowork. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Maidang1/open-claude-cowork/main/AGENTS.mdgit clone --depth 1 https://github.com/Maidang1/open-claude-coworkWrote 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.
[](https://agentmods.dev/instructions/maidang1/open-claude-cowork/agents-md)<a href="https://agentmods.dev/instructions/maidang1/open-claude-cowork/agents-md"><img src="https://agentmods.dev/badge/instructions/maidang1/open-claude-cowork/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.
<a href="https://agentmods.dev/instructions/maidang1/open-claude-cowork/agents-md"><img src="https://agentmods.dev/badge/instructions/maidang1/open-claude-cowork/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00614 | $0.00614 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
open-claude-cowork 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This is an Electron + React + TypeScript desktop app.
src/main/: Electron “main” process (ACP client, SQLite, IPC, filesystem/runtime helpers).src/render/: React “renderer” UI (components, hooks, state, agent presets/icons).src/types/: Shared TypeScript types.builder/: Rsbuild configs formainandrender.public/andassets/: Static assets (icons/wallpapers, etc.).env/: Build/runtime env templates (per-platform.env.*).
Notes:
release/is generated output and is git-ignored (see.gitignore).
Build, Test, and Development Commands
Use pnpm (see package.json#packageManager).
pnpm install: Install deps (runs Electron postinstall + native deps setup).pnpm run dev: Local dev (usesplopto orchestrate main + renderer).pnpm run dev:render: Start only the renderer dev server.pnpm run dev:main: Start only the main process (vianodemon.json).pnpm run lint: Run Biome checks + auto-fix forsrc/.pnpm run build: Production build (interactive platform selection).pnpm run build:darwin|build:win32|build:linux: Platform-specific builds.pnpm run rebuild:main: Build main process and launch Electron usingrelease/dist/main/index.js.
Coding Style & Naming Conventions
- Indentation: 2 spaces, line width 100 (Biome:
biome.json). - Quotes: double quotes (Biome JS/TS formatter).
- TypeScript:
strict: true(tsconfig.json), prefer explicit types at boundaries. - Paths: use aliases where appropriate (
@main/*,@render/*,@components/*, etc.).
Testing Guidelines
There is no repository-level test runner wired (no test script/config). Changes should include a quick manual check:
- Run
pnpm run devand exercise the relevant UI/IPC/agent flow. - For build-related changes, verify with a platform build script (e.g.
pnpm run build:darwin).
Commit & Pull Request Guidelines
Commits generally follow Conventional Commits style (examples in history): feat:, fix:, refactor:, chore:, style:, release:.
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.
- 10d ago First seen · 53 lines · 614 tokens per session scan A a7a3d848c79d
open-claude-cowork AGENTS.md is an instructions file published in the GitHub repository Maidang1/open-claude-cowork (11 stars, last pushed 7mo ago), licensed MIT. It adds 614 tokens to every session, about $0.0031 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.
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.
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.
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).
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.
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).
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.