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/illustrationnpx skills add masayan1126/masayan-uni-code-plugins --skill illustrationgit clone --depth 1 https://github.com/masayan1126/masayan-uni-code-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.00056 | $0.01025 |
| Opus 5 | $0.00028 | $0.00513 |
| Sonnet 5 | $0.00011 | $0.00205 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
creating-illustrations 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
汎用イラストプロンプト作成
ワークフロー
- 用途確認: 用途を確認（アルバムカバー/商品写真/コンセプトアート/etc.）
- プリセット確認: 使用可能なプリセットの利用有無
- プリセットあり → PRESETS.md から設定を適用
- プリセットなし → ステップ3へ
- 要件収集:
AskUserQuestionツールで6つの要素をヒアリング- 主題・被写体: メインの対象と詳細
- 色彩: カラーパレット、カラーコード
- スタイル・画風: アニメ調/写実的/etc.
- 雰囲気: ムード、感情
- （オプション）光源・照明、視点・構図
- 情報構造化: 6つの原則に基づいて収集した情報を整理
- AIっぽさ緩和オプション確認: ANTI_AI_STYLE.md 参照
- 「ベタ塗り」「デフォルメされたフォルム」を含めるか確認
- プロンプト生成: PROMPT_TEMPLATE.md 使用して実行可能なプロンプトを生成
- クリップボードコピー:
AskUserQuestionで選択肢提示後、pbcopy（Mac）でコピー - アイデア確認:
progress/ideas.mdをチェックし、該当するアイデアがあれば提案 - 成果物保存:
- プロンプト:
output/illustration/{タイトル}.md（ディレクトリがなければ作成） - 生成画像:
output/illustration/images/{タイトル}.png
- プロンプト:
- 進捗更新:
progress/ideas.mdを更新（完了したアイデアにチェック）
6つの原則
高品質プロンプト作成の実証済みテクニック:
| 原則 | 説明 |
|---|---|
| 優先順位 | 最重要要素を冒頭に配置 |
| 具体性 | 単語ではなく詳細な説明を追加 |
| 光源 | 光の方向、質、色温度を指定 |
| 視点 | カメラアングルと構図を明確化 |
| 画風 | 様式（印象派、アニメ等）を指定 |
| 色調 | カラーパレットで雰囲気を統一 |
詳細は TECHNIQUES.md 参照
参照ファイル
- TECHNIQUES.md: 6つのテクニック詳細
- PRESETS.md: プリセット集（レトロオブジェクト/ゆるふわインコ）
- PROMPT_TEMPLATE.md: テンプレート
プリセット一覧
| プリセット名 | 概要 |
|---|---|
| レトロオブジェクト | 80-90年代ノスタルジック、ローファイアニメスタイル |
| ゆるふわインコ | パステルカラー、癒し系手描き風イラスト |
必須ルール
- 優先順位を守り最重要要素を冒頭に
- 具体的な詳細を含める（曖昧表現を避ける）
- 光源・色彩を明確に指定してAI感を軽減
- カラーコード（#XXXXXX）で正確な色指定
- ネガティブプロンプトで不要要素を除外
著作権への配慮
- 特定のアーティスト名・作品名の使用を避ける
- スタイル・様式の一般的な説明を使用（例: "impressionist style" ✓ / "in the style of [artist]" ✗）
- 不適切・差別的な表現を避ける
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 · 72 lines · 56 tokens per session scan A 2db271356ba2
creating-illustrations is a skill published in the GitHub repository masayan1126/masayan-uni-code-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,025 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-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…