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 commands/adityaraj0421/naksha-studio/chart-designgit clone --depth 1 https://github.com/Adityaraj0421/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/chart-design)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/chart-design"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/chart-design.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.00033 | $0.01552 |
| Opus 5 | $0.00016 | $0.00776 |
| Sonnet 5 | $0.00007 | $0.00310 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
chart-design 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 5d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/chart-design
Design a data visualization: select the right chart type, apply accessible colors, add meaningful annotations, and produce production-ready HTML/CSS/JS with Chart.js (or vanilla SVG for simple charts).
Usage: /chart-design <description>
Examples:
/chart-design monthly revenue trend for 2025/chart-design part-to-whole breakdown of user acquisition channels/chart-design scatter plot: ad spend vs conversion rate/chart-design --library d3 geographic distribution by US state
Process
1. Parse the Request
Extract from $ARGUMENTS:
- Data relationship: What story is being told? (trend, comparison, distribution, correlation, part-to-whole, ranking, geographic, flow)
- Data shape: How many series? Continuous vs discrete? Time-based?
- Library:
--library chart.js(default) |d3|recharts|vanilla - Accessibility: Any colorblind-safe requirements? (
--a11yflag or always default to accessible palette) - Style:
--style darkfor dark backgrounds,--style minimalfor clean axes
2. Select Chart Type
Apply the chart type selection matrix from the Data Viz Designer reference:
| Data relationship → | Recommended chart |
|---|---|
| Trend over time (continuous) | Line chart |
| Trend over time (discrete periods) | Vertical bar chart |
| Part-to-whole (≤ 5 categories) | Donut chart |
| Part-to-whole (many categories) | Stacked bar |
| Comparison across categories | Grouped bar chart |
| Single metric vs target | Bullet chart |
| Distribution of one variable | Histogram |
| Correlation between 2 variables | Scatter plot |
| Ranking with long labels | Horizontal bar |
| Hierarchical proportions | Treemap |
| Flow between stages | Sankey diagram |
Reject anti-patterns: If the request implies a 3D chart, dual Y-axis, or pie with > 5 slices, note the issue and recommend the appropriate alternative.
3. Design the Color Palette
Apply palette based on the data type:
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.
- 5d ago First seen · 162 lines · 33 tokens per session scan A 2a151809f6b6
chart-design is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,552 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-30.
Other commands, from other repositories
full-diagnostic
Comprehensive design system health sweep.
release-check
Pre-release validation pipeline for a component.
describe-component
Generate an AI-optimised component description.
docs-coverage
Audit whether your documentation surface keeps pace with your components.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.