agentmods.dev

ClawDEA CLAUDE.md

Repository instructions for ClawDEA, an IntelliJ plugin that connects Claude Code, a coding assistant, to the IntelliJ development environment.

In plain words
What is it for?
Use them when compiling the project, running tests, launching the plugin in IntelliJ, checking its architecture, or preparing a plugin release.
Why use it?
They explain how to build, test, run, and understand the plugin, including known build and test limitations.

Instructions file

8 6d ago A scan 2,071 tokens original Apache-2.0
View the source file adobe/ClawDEA
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/adobe/clawdea/claude-md
Clone the repo
git clone --depth 1 https://github.com/adobe/ClawDEA
Per session 2,071 This file is loaded in full into every session.
When invoked 2,071 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.02071 $0.02071
Opus 5 $0.01035 $0.01035
Sonnet 5 $0.00414 $0.00414
Haiku 4.5 $0.00207 $0.00207

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

Security

Grade A, and why

ClawDEA 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 2d 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 · 91 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Build & Test

./gradlew compileKotlin                    # Fast compile check
./gradlew test                             # Unit tests (headless-safe subset)
./gradlew build -x buildSearchableOptions  # Full build; skip searchable options if IDE is running
./gradlew runIde                           # Launch sandboxed IDE with plugin loaded

buildSearchableOptions fails when IntelliJ is already running ("Only one instance of IDEA can be run at a time") — always pass -x buildSearchableOptions in that case.

The plugin zip lands in build/distributions/ClawDEA-<version>.zip.

Fixture-based tests (IndexQueryHandlerTest) are excluded from ./gradlew test because they hang headlessly — run those from the IDE test runner only.

Version is in gradle.properties (pluginVersion). Bump it there for releases.

Architecture

ClawDEA is an IntelliJ plugin that wraps the Claude Code CLI (claude) as a subprocess and exposes IntelliJ's indices back to Claude via a local MCP HTTP server.

Data flow

User ←→ ChatPanel (JCEF) ←→ CliBridge ←→ CliProcess (claude --output-format stream-json)
                                              ↕ MCP HTTP (127.0.0.1:random)
                                          McpServer → McpToolRouter → {Index, IDE, Context, EditReview} tools
  1. ChatPanel renders a JCEF browser, handles user input, slash commands, and streams CLI events into HTML.
  2. CliBridge owns the CliProcess lifecycle and exposes a SharedFlow<CliEvent>.
  3. CliProcess spawns claude in --output-format stream-json mode with --print-turn-events. It writes a temp MCP config file pointing the CLI at the local McpServer.
  4. CliEventParser parses NDJSON lines into a sealed CliEvent hierarchy (SystemInit, TextDelta, AssistantMessage, ToolUse, ToolResult, Result, AuthFailure, TaskEvent).
  5. McpServer is a project-level service (HttpServer on 127.0.0.1:0) that routes JSON-RPC requests through McpToolRouter to the tool groups: McpIndexTools (find files/symbols/usages/callers), McpSearchTextTool (literal/regex content search), McpIdeTools (diagnostics, resolve symbol), McpContextTool (project context), McpPrimerTool (project primer), McpWikiTools (docs/llm-wiki/ search + read), McpWorkspaceTools (sibling-repo navigation), McpEditReviewTools (propose_edit/propose_write/propose_multi_edit), McpDebugTools (21 debugger tools), McpPermissionPromptTool (tool-call approval gate).

Read the full file on GitHub · 91 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. 2d ago First seen · 91 lines · 2,071 tokens per session scan A 2af5efc0d57d

Subscribe to this mod's changes

ClawDEA CLAUDE.md is an instructions file published in the GitHub repository adobe/ClawDEA (8 stars, last pushed 6d ago), licensed Apache-2.0. It adds 2,071 tokens to every session, about $0.0104 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.

Git and workflowPlanningTesting
Related

Other instructions, from other repositories

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

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

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

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

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