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/masayan1126/masayan-uni-code-plugins/tech-diagramnpx skills add masayan1126/masayan-uni-code-plugins --skill tech-diagramgit clone --depth 1 https://github.com/masayan1126/masayan-uni-code-pluginsWrote 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/masayan1126/masayan-uni-code-plugins/tech-diagram)<a href="https://agentmods.dev/skills/masayan1126/masayan-uni-code-plugins/tech-diagram"><img src="https://agentmods.dev/badge/skills/masayan1126/masayan-uni-code-plugins/tech-diagram.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.00040 | $0.00616 |
| Opus 5 | $0.00020 | $0.00308 |
| Sonnet 5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
creating-tech-diagrams 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.
What it actually says
テック・AI解説用図解作成
注: 生成したプロンプトを画像生成AIに入力する際は、キャラクターの元画像を一緒に添付してください（解説役として配置）。
ワークフロー
- アイデア確認:
progress/ideas.mdをチェックし、該当するアイデアがあれば提案 - トピック確認: 新規入力 or アイデアリストから選択
- 画像テイスト確認: ユーザーに以下から選択してもらう
- クリーン: 整った線、モダンなインフォグラフィック風
- 手書き風: ラフスケッチ、走り書き風、親しみやすい雰囲気
- 図解タイプ選択:
- フローチャート型: プロセス説明
- 比較表型: 技術比較
- 概念図型: 抽象概念
- アーキテクチャ図型: システム構成
- タイムライン型: 歴史・進化
- 構成要素設計: 3-5個のメイン要素に絞る
- AIっぽさ緩和オプション確認: ANTI_AI_STYLE.md 参照
- 図解系は「ベタ塗り」のみ推奨
- プロンプト生成: PROMPT_TEMPLATE.md 使用（選択したテイストを反映）
- Xポスト文面生成
- 成果物保存:
- プロンプト:
output/tech-diagram/{タイトル}.md（ディレクトリがなければ作成） - 生成画像:
output/tech-diagram/images/{タイトル}.png
- プロンプト:
- 進捗更新:
progress/ideas.mdを更新（完了したアイデアにチェック）
参照ファイル
- STYLES.md: スタイル定義
- PROMPT_TEMPLATE.md: テンプレート
- EXAMPLES.md: サンプル
必須ルール
- テキストは日本語
- 画像上部にタイトル配置
- 画像テイストは必ずユーザーに確認してからプロンプト生成
What ships with it
3 files 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.
- 3d ago First seen · 44 lines · 40 tokens per session scan A 92f6fe427ae0
creating-tech-diagrams is a skill published in the GitHub repository masayan1126/masayan-uni-code-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 616 once invoked, about $0.0002 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
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…