DEDUPEDWho it is forTeam lead documenting how an internal AI agent is wired before a security or ops review
The problemReviewers ask where data goes and who approves actions, and nobody has a single picture to point at.
The outcomeA diagram showing the agent, its tools, data flows and approval points that can be attached to a review document.
What you need first
- An Agent Skills compatible host such as Claude Code, Codex, Cursor, Qoder, GitHub Copilot, Gemini CLI, Cline, Windsurf or Amp
- Node.js for the npx install command
- A browser to open the generated HTML file
- Optional: a public website URL for brand onboarding
Steps
- Install the skill with: npx skills add cathrynlavery/diagram-design
- List your agent's tools, data sources and approval steps in a short prompt.
- Ask for a diagram that shows data flows and where a human approves actions.
- Walk the reviewers through the HTML file and correct anything they spot.
Prompt for your agent
Using diagram-design, draw our agent setup for <agent name>: the tools it can call, where data flows, and where a person must approve. Mark any boundary where data leaves our systems so I can double-check it.
Caveat. The diagram shows what you tell it, not what the agent actually does at runtime. Do not use it as proof of a security boundary without verifying the real config.
About diagram-design
An agent skill that draws clean diagrams as a single HTML and SVG file in your brand. Part of this week's top 10 repos: ranked #8 on Repo Radar. View cathrynlavery/diagram-design on GitHub.
More with diagram-design
- Draw an architecture diagram for your README without a design tool Describe your app in plain words and get a clean HTML and SVG diagram to drop into your README.
- Draw the plan before your agent writes the code Ask for a flow or sequence diagram of a proposed change and approve the design first.
- Map an unfamiliar repo's components before you change it Have your agent read a codebase and draw its parts and connections so you can orient before editing.
- Pair diagrams with a video skill to explain a GitHub repo Use the diagram skill alongside HyperFrames to turn a repo README into a short explainer video.
- Make every diagram match your website's colors and fonts Give the skill your site URL once and every later diagram uses your palette and fonts.
- Redraw an old Mermaid or draw.io diagram in a cleaner style Import an existing Mermaid, draw.io or Excalidraw file and get it back as a polished editorial diagram.
- Add light motion to a diagram that explains steps in order Turn on optional motion so a process diagram reveals its steps one after another.
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page