OpenCove is a desktop workspace that places AI coding-agent sessions, terminals, tasks, and notes together on an infinite two-dimensional canvas. It is designed for people running Claude Code, Codex, and similar terminal-based agents who need to view parallel work, preserve context, and resume projects across sessions.
Borrowing it
Nothing to install: this file belongs to DeadWaveWave/opencove. 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/DeadWaveWave/opencove/main/AGENTS.mdgit clone --depth 1 https://github.com/DeadWaveWave/opencoveWrote 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/deadwavewave/opencove/agents-md)<a href="https://agentmods.dev/instructions/deadwavewave/opencove/agents-md"><img src="https://agentmods.dev/badge/instructions/deadwavewave/opencove/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/deadwavewave/opencove/agents-md"><img src="https://agentmods.dev/badge/instructions/deadwavewave/opencove/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.01282 | $0.01282 |
| Opus 5.5 | $0.00513 | $0.00513 |
| Sonnet 5.5 | $0.00256 | $0.00256 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
opencove 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 16d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Prompt: OpenCove Project AI Developer Agent
This file defines the Unified Execution Standard for all Agents (including Codex/Claude Code) working on the OpenCove repository.
Your primary directive is to Read DEVELOPMENT.md first and strictly adhere to its rules. Follow the documented process before acting, and convert good engineering judgment into explicit steps, checks, and deliverables.
Target: Rapid iteration of core features while ensuring regression testing, traceability, and acceptance.
1. Core Directives & Golden Rules
- Top-tier Architecture Mindset: Never use a "patch" mindset. Before coding, simulate how top-tier teams, famous open-source projects, or industry leaders would solve this problem. For mature industry problems, you MUST research them per
REFERENCE_RESEARCH_METHOD.md. - Golden Rule: ALWAYS read
DEVELOPMENT.mdat the start of a task. It is the default source of truth for architecture, workflow, commands, and detailed execution method. - Monorepo: Always set correct CWD. Follow the file structure defined in
DEVELOPMENT.md. - Tooling Integrity: NEVER edit
lockfiles or scripted generated code manually. Use the commands defined in the relevant moduleDEVELOPMENT.md(linked from rootDEVELOPMENT.md). - Commit Code, Not Analysis: Only code and this project's own long-lived documentation get committed. Research reports and per-PR review/acceptance write-ups are local decision artifacts — keep them out of the repo unless explicitly asked, and put review conclusions in the PR instead. If a finding has lasting value, fold the conclusion into the relevant project doc rather than committing the report.
- Keep AGENTS Concise:
AGENTS.mdshould state key directives, decision gates, and non-negotiables only. Detailed methods, examples, and step-by-step execution guidance belong inDEVELOPMENT.mdor topic docs.
2. Decision Framework (Small vs Large)
On every instruction, triage the request and tell the user whether it is Small or Large.
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.
- 16d ago Changed · +1 lines · +99 tokens per session 9347ada62663
- 1mo ago First seen · 72 lines · 1,183 tokens per session scan A f35ec577b24f
opencove AGENTS.md is an instructions file published in the GitHub repository DeadWaveWave/opencove (1,641 stars, last pushed 11d ago), licensed MIT. It adds 1,282 tokens to every session, about $0.0051 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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.