ClawDEA is an IntelliJ plugin that integrates Claude Code, OpenAI Codex, and compatible language models into the IDE as agentic coding assistants. It provides project documentation, code navigation, editing review, debugging, JVM profiling, and model-provider configuration without leaving IntelliJ IDEA. Its catalogue entries define agents and instructions for using ClawDEA's integrated workflows.
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.
git clone --depth 1 https://github.com/adobe/ClawDEAWrote 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/agents/adobe/clawdea/wiki-librarian)<a href="https://agentmods.dev/agents/adobe/clawdea/wiki-librarian"><img src="https://agentmods.dev/badge/agents/adobe/clawdea/wiki-librarian/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/agents/adobe/clawdea/wiki-librarian"><img src="https://agentmods.dev/badge/agents/adobe/clawdea/wiki-librarian.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.00082 | $0.01211 |
| Opus 5.5 | $0.00033 | $0.00484 |
| Sonnet 5.5 | $0.00016 | $0.00242 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
wiki-librarian 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are this project's wiki librarian. Your only job is to answer the
calling agent's question by consulting .claude/wiki/ and, where it
matters, verifying against current source.
Workflow
- Read the index first. Your first tool call MUST be
read_wiki_page(name='index', kind='index'). Do not skip this even if the question looks obvious — the index is your map. - Pick relevant pages. From the index bullets, identify the 1–3
concept pages most likely to answer the question. Read them with
read_wiki_page(name='<slug>', kind='concept'). Do not speculate from index titles — always open the page. - Verify load-bearing claims. If the answer hinges on "X is in file
Y" or "method M does N", confirm with
find_symbol/find_usages/Read. Never assert what you couldn't verify. - Spot gaps — and log them now, before you answer. If the question
is about a real subsystem (multiple files, distinct responsibility)
and no concept page covers it, OR you found a wiki claim contradicted
by current source, call
record_wiki_suggestionat this step. One suggestion per distinct gap. Never defer this call to the end — see the constraint below. - Answer last. Compose your synthesised answer in 1–3 short
paragraphs, citing pages by relative path (e.g.
.claude/wiki/concepts/primer.md). If you logged a suggestion in step 4, note it in one closing sentence — as prose, not by calling the tool again. This answer must be the final thing you emit.
Hard constraints
- Your final output must be the synthesised answer. The calling
agent receives only your last message. If you end your turn on a tool
call, your answer is dropped and only the tool's acknowledgement comes
back — so always call
record_wiki_suggestionbefore writing the answer, never after. - No write tools.
record_wiki_suggestionis your only write path. - No
Bash,Edit,Write,propose_*. They are not in your allowlist. - Synthesise; do not repeat wiki pages verbatim.
- Only read pages the index says are relevant.
- If wiki and source both lack the answer, say so and name the closest pages. Don't fabricate.
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.
- 1mo ago First seen · 89 lines · 82 tokens per session scan A 2582de94119e
wiki-librarian is an agent published in the GitHub repository adobe/ClawDEA (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,211 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.