archeyes

An interactive architecture diagram tool for discussing software plans, technical designs, features, and existing codebases. Architecture diagrams show the parts of a system and how they relate.

In plain words
What is it for?
Use it to visualize an implementation plan, inspect a codebase or feature design, edit the resulting diagram, and send those edits back to the coding agent.
Why use it?
It gives an agent structured feedback about a design through a visual graph rather than relying only on a text conversation.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add thisAAY/archeyes
agentmods
npx agentmods add plugins/thisaay/archeyes/marketplace
Clone the repo
git clone --depth 1 https://github.com/thisAAY/archeyes

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

archeyes 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-plugin/marketplace.json · 16 lines

What it actually says

{
  "name": "archeyes",
  "description": "ArchEyes — a diagram you talk back to. Visualize a plan, an existing codebase, or a feature, then send structured feedback to your agent.",
  "owner": { "name": "thisAAY", "url": "https://github.com/thisAAY" },
  "plugins": [
    {
      "name": "archeyes",
      "source": "./plugins/archeyes",
      "description": "Render an implementation plan, tech spec, or codebase as an interactive architecture graph you edit directly; the structured edits flow back to the agent. Skill: /archeyes:review (needs `npx archeyes` — install `archeyes` from npm).",
      "version": "0.2.0",
      "category": "workflow",
      "tags": ["architecture", "diagram", "plan", "review"]
    }
  ]
}
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 · 16 lines scan A 7b99d1d4c49d

Subscribe to this mod's changes

archeyes is a plugin published in the GitHub repository thisAAY/archeyes (7 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.