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 skills add DavidROliverBA/ArchitectKB --skill diagram-reviewgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/diagram-review)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/diagram-review"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/diagram-review/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/skills/davidroliverba/architectkb/diagram-review"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/diagram-review.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.00009 | $0.01190 |
| Opus 5 | $0.00005 | $0.00595 |
| Sonnet 5 | $0.00002 | $0.00238 |
| Haiku 4.5 | $0.00001 | $0.00119 |
Grade A, and why
diagram-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 11d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/diagram-review
Perform comprehensive analysis of architecture diagrams, flowcharts, and technical drawings using Sonnet sub-agents.
Usage
/diagram-review <image-path>
/diagram-review Attachments/architecture-diagram.png
/diagram-review Attachments/data-flow.png --type "C4"
/diagram-review Attachments/process-flow.png --project "Integration Project"
Instructions
This skill uses Sonnet model sub-agents for thorough diagram analysis with vision capabilities.
Phase 1: Diagram Loading
- Verify the image exists at the specified path
- Identify diagram type if specified or detect automatically
- Load project context if provided
Phase 2: Comprehensive Analysis (Sonnet Sub-Agents)
Launch these sub-agents using model: "sonnet":
Agent 1: Component Extraction (Sonnet)
Task: Extract all components and elements from the diagram
- Read the image file using the Read tool
- Identify all boxes, shapes, and containers
- Extract all labels and text
- Note icons, symbols, and visual indicators
- Capture any legend or key information
Return: Complete component inventory with labels
Agent 2: Relationship Mapping (Sonnet)
Task: Map all connections and relationships
- Read the image file
- Identify all lines, arrows, and connectors
- Determine direction of data/process flow
- Note relationship types (dependency, data flow, API call, etc.)
- Identify any protocols or technologies on connections
- Map parent-child or containment relationships
Return: Relationship matrix with flow directions
Agent 3: Architecture Pattern Analysis (Sonnet)
Task: Analyse architectural patterns and quality
- Read the image file
- Identify the diagram type (C4, UML, flowchart, network, etc.)
- Recognise architectural patterns (microservices, layered, event-driven)
- Assess separation of concerns
- Identify potential single points of failure
- Note security boundaries if visible
- Evaluate completeness and clarity
- **Readability assessment:**
- Count edge crossings (target: <5 for complex, 0 for simple)
- Check visual hierarchy (is the system boundary the most prominent element?)
- Verify consistent flow direction (L→R or T→B, not mixed)
- Assess Gestalt proximity compliance (are related elements grouped together?)
- Check single abstraction level (no database tables on container diagrams)
Return: Pattern analysis with architectural assessment and readability score
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.
- 11d ago First seen · 193 lines · 9 tokens per session scan A b5fe8785c4c7
diagram-review is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,190 once invoked, about $0.0000 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…