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.
npx agentmods add skills/thisaay/archeyes/reviewnpx skills add thisAAY/archeyes --skill reviewgit clone --depth 1 https://github.com/thisAAY/archeyesWrote 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/skills/thisaay/archeyes/review)<a href="https://agentmods.dev/skills/thisaay/archeyes/review"><img src="https://agentmods.dev/badge/skills/thisaay/archeyes/review.svg" alt="Measured on agentmods" 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 | $0.00094 | $0.02273 |
| Opus 5 | $0.00047 | $0.01137 |
| Sonnet 5 | $0.00019 | $0.00455 |
| Haiku 4.5 | $0.00009 | $0.00227 |
Grade A, and why
review 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 3d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchEyes — bidirectional plan diagrams
ArchEyes makes the diagram an input device. You render the plan as a graph; the developer manipulates it directly; their edits come back to you as a structured diff with exact node/edge IDs — zero prose disambiguation. You revise and re-render. Loop until they approve.
You are the parser. ArchEyes' code never reads a plan. You author plan-graph.json
from whatever is at hand: a fresh plan-mode plan, an existing markdown tech spec, the
codebase itself, or current + planned together (which powers the before/after diff).
Don't interview the developer first. The graph is the question — render your best guess and let them fix it on the canvas. That's faster and more precise than terminal Q&A. The one thing the canvas can't express as an edit is a framing choice: altitude (system vs service vs class level) and before/after diff vs single-state graph. Pick one, state which you picked in your terminal message, and ask up front only when you're genuinely torn — fixing altitude visually means the developer deleting and merging a dozen nodes by hand.
The loop
- Author the graph. Write
plan-graph.json(schema below). Keep your prose plan too — it's the same structure, rendered as text, and the accessible representation. - Run the review.
npx archeyes review plan-graph.json(orarcheyes review …if installed). It serves a canvas, opens the browser, and BLOCKS until the developer acts. - Read the feedback. The command prints ONE JSON envelope to stdout and exits.
- exit
0→ an envelope was printed (revise|approve|cancel). Act on it. - exit non-zero → no feedback (idle timeout / error). If it says the server is still
up, run
archeyes review --resumeto re-attach. Otherwise start a new round.
- exit
- Interpret + revise (guide below). Rewrite
plan-graph.jsonAND your prose plan. - Re-render. Run
archeyes review plan-graph.jsonagain. Loop.action: "approve"→ the current graph + plan are final. Stop.action: "cancel"→ stop the loop, keep the plan as-is, ask the developer in the terminal how they want to proceed.
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.
- 3d ago First seen · 149 lines · 94 tokens per session scan A 3d6b6a9c34f2
review is a skill published in the GitHub repository thisAAY/archeyes (7 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 2,273 once invoked, about $0.0005 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.
Other skills, from other repositories
terra-form
Terraform이 있는 클라우드 인프라(AWS·GCP·Azure 등)를 그린다. AWS는 공식 아이콘 838종·AZ×티어 격자·스팬 overlay, 타 클라우드는 카테고리 카드+확장 아이콘으로. 내장 엔진(TS DSL → 자동배치 → 셀프컨테인드 HTML)으로 렌더하고 zzon-doc 통합 문서/zzon-wiki manifest에 정식 편입한다. "tf 인프라 그려줘", "테라폼 구조 시각화", zzon-wiki의 인프라/배포 문서에 사용한다.
zzon-doc
코드베이스나 설명을 분석해 아키텍처/인프라/ERD/Claude 에이전트 다이어그램을 그린다. 동봉 엔진(TS DSL → 자동배치 → 셀프컨테인드 인터랙티브 .html)으로 렌더한다. "아키텍처 그려줘", "인프라 다이어그램", "ERD 만들어줘", "이 시스템 구조를 시각화" 같은 요청에 사용한다.
archify
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…
hooked-ux
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building…
create-website
Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing…