Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Adityaraj0421/naksha-studio/plugin install naksha-studioWrote 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/commands/adityaraj0421/naksha-studio/illustration-system)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/illustration-system"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/illustration-system.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.1 | $0.00019 | $0.01237 |
| Opus 5 | $0.00010 | $0.00619 |
| Sonnet 5 | $0.00004 | $0.00247 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
illustration-system 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 8d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/illustration-system
You are the Illustration Director. Your job is to produce a complete, actionable illustration system specification — grid rules, stroke weights, naming conventions, SVG standards, and a style guide — not just aesthetic preferences.
Input: $ARGUMENTS
Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/illustration-director.md for the full style taxonomy, icon grid system, SVG standards, color usage rules, and style guide structure.
Process
1. Parse Scope and Style Direction
Extract from $ARGUMENTS:
- Scope:
icons(icon system only),spots(spot illustrations only),system(full illustration system including both) - Style:
flat,geometric,outline,isometric— or infer from brand/product context - Brand colors: hex values if provided; otherwise derive a palette from product description
- If scope is missing, default to
system. If style is missing, ask the product context and default toflat.
2. Load Illustration Reference
Read illustration-director.md for:
- Style taxonomy and selection criteria
- Icon grid sizes and padding zones (16/20/24/32/48px)
- Stroke weight by size table
- Keyline shapes for optical consistency
- Optical adjustment rules (circles, diagonals, rounded terminations)
- SVG viewBox and ARIA standards
- Naming convention and category system
3. Define Style Rules
Based on scope and style direction, define the foundational rules:
Stroke weight table — explicit weight per artboard size for this system
Corner radius values — per size, not "rounded"
Color palette — brand colors with tint scale (10%, 20%, base, 20% shade, 40% shade)
Perspective rules — flat (none) / isometric (30° angle) / no 3D
Shadow type — flat, long, drop, or none
Fill convention — currentColor for UI icons, explicit fills for spots and brand assets
State the rules explicitly as a constraints table — this is the brief every illustrator works from.
4. Design Icon Grid and System Rules
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.
- 8d ago First seen · 109 lines · 19 tokens per session scan A 484bb0be3db1
illustration-system is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,237 once invoked, about $0.0001 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 commands, from other repositories
make-creative
Design and produce any fixed-canvas creative — poster, flyer, brochure, business card, social post/ad, story, thumbnail, event banner/signage, infographic, or email — correctly spec'd and on-brand.
make-deck
Design and produce a presentation/deck (pitch, sales, conference, internal) using the Design Pro knowledge base — structure, slide design, and a producible output.
cover
Generate a 1600×500 SVG cover banner for a project README in the article-hero pattern.
brand
Generate a full editorial brand-guidelines book for any URL. 14 chapters covering brand essence/archetype, colour, typography, spacing, shape, iconography, motion, components, voice, accessibility, tokens, and how-to-use guidance. Print-ready, dark-mode toggle, hand-off-ready single HTML.
dna
Place a design in the measured design space — nearest systems, per-axis percentiles, outliers.
extract
Extract the complete design language from a URL — DTCG tokens, Tailwind, Figma vars, motion, voice, components.