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/agentic-dev3o/devx-plugins/banana-illustrationnpx skills add agentic-dev3o/devx-plugins --skill banana-illustrationgit clone --depth 1 https://github.com/agentic-dev3o/devx-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.00077 | $0.00830 |
| Opus 5 | $0.00039 | $0.00415 |
| Sonnet 5 | $0.00015 | $0.00166 |
| Haiku 4.5 | $0.00008 | $0.00083 |
Grade A, and why
banana-illustration 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Illustration Generator
Input: $ARGUMENTS (optional — subject and style description)
If $ARGUMENTS is provided, use it as the illustration brief and skip to prompt building. If empty, ask about subject and style.
Requirements
uvinstalledGEMINI_API_KEYenvironment variable set (get one at https://aistudio.google.com/apikey)
Workflow
- Understand — Parse the user's request. Identify the subject, narrative action, environment, and desired art style. If the style is ambiguous, ask ONE clarifying question or default to flat vector.
- Build prompt — Apply the Prompt Formula below to construct a detailed, positive-framed illustration description.
- Configure — Select aspect ratio and resolution from the Domain Defaults table.
- Generate — Run the script.
- Deliver — Report the saved file path. Do NOT read the image file back. Offer to iterate: swap style, adjust palette, or tweak composition.
Prompt Formula
[Subject/Character] + [Narrative Action] + [Illustrated Environment] + [Balanced Composition] + [Explicit Art Style]
Style Detection Rules
| User Keywords | Resolved Style |
|---|---|
| "flat" / "vector" | Flat vector with solid fills, clean edges |
| "watercolor" | Wet-on-wet watercolor with paper texture, visible brushstrokes |
| "3D" / "clay" | Pixar-style clay render, soft shadows |
| "pixel" | Pixel art with visible grid, limited palette |
| "isometric" | Isometric projection, no perspective vanishing points |
| "line art" / "ink" | Consistent weight ink lines, minimal fills |
| Ambiguous | Default to flat vector |
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 · 86 lines · 77 tokens per session scan A ec5c7f2c8928
banana-illustration is a skill published in the GitHub repository agentic-dev3o/devx-plugins (11 stars, last pushed 15d ago), licensed MIT. It adds 77 tokens to every session and 830 once invoked, about $0.0004 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…