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/roboco-io/plugins/draw-diagramnpx skills add roboco-io/plugins --skill draw-diagramgit clone --depth 1 https://github.com/roboco-io/pluginsWhat 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.00067 | $0.03407 |
| Opus 5 | $0.00034 | $0.01703 |
| Sonnet 5 | $0.00013 | $0.00681 |
| Haiku 4.5 | $0.00007 | $0.00341 |
Grade A, and why
draw-diagram 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.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draw.io Diagram Skill
.drawio XML 파일을 직접 생성하여 다이어그램을 만듭니다. draw.io는 XML 기반 포맷이므로 AI가 직접 생성 가능합니다.
지원 다이어그램 유형
| 유형 | 설명 |
|---|---|
| Architecture | 시스템/클라우드 아키텍처 다이어그램 |
| Flowchart | 프로세스 흐름도 |
| Sequence | 시퀀스 다이어그램 |
| ERD | Entity-Relationship 다이어그램 |
| Network | 네트워크 토폴로지 |
| C4 Model | Context, Container, Component, Code 다이어그램 |
.drawio XML 기본 구조
모든 다이어그램은 이 기본 구조를 따릅니다:
<mxfile host="app.diagrams.net" modified="2024-01-01T00:00:00.000Z" agent="Claude" version="24.0.0" type="device">
<diagram id="diagram-1" name="Page-1">
<mxGraphModel dx="1422" dy="762" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
<root>
<mxCell id="0" />
<mxCell id="1" parent="0" />
<!-- 여기에 도형과 연결선 추가 -->
</root>
</mxGraphModel>
</diagram>
</mxfile>
필수 규칙:
id="0"과id="1"(parent) mxCell은 항상 포함- 모든 도형의
parent="1",vertex="1" - 모든 연결선의
parent="1",edge="1",source,target지정 - id는 고유해야 함 (숫자 또는 문자열)
도형 (Vertex) 작성법
기본 사각형
<mxCell id="2" value="서비스명" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;" vertex="1" parent="1">
<mxGeometry x="100" y="100" width="120" height="60" as="geometry" />
</mxCell>
주요 스타일 속성
| 속성 | 값 예시 | 설명 |
|---|---|---|
rounded |
0, 1 |
모서리 둥글게 |
fillColor |
#dae8fc |
배경색 |
strokeColor |
#6c8ebf |
테두리색 |
fontColor |
#232F3E |
글자색 |
fontSize |
12 |
글자 크기 |
fontStyle |
0=일반, 1=볼드, 2=이탤릭 |
글자 스타일 |
whiteSpace |
wrap |
텍스트 줄바꿈 |
html |
1 |
HTML 렌더링 |
shape |
mxgraph.aws4.lambda |
커스텀 도형 |
aspect |
fixed |
비율 고정 |
verticalLabelPosition |
bottom |
레이블 위치 |
verticalAlign |
top |
레이블 세로 정렬 |
dashed |
0, 1 |
점선 테두리 |
기본 도형 종류
shape=ellipse # 원/타원
shape=rhombus # 마름모 (조건 분기)
shape=parallelogram # 평행사변형
shape=hexagon # 육각형
shape=cylinder3 # 실린더 (DB)
shape=document # 문서
shape=process # 프로세스
shape=mxgraph.flowchart.annotation_1 # 주석
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 271 lines · 67 tokens per session scan A 56e9291f3630
draw-diagram is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 3,407 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…