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/reggiechan74/cc-plugins/d3jsnpx skills add reggiechan74/cc-plugins --skill d3jsgit clone --depth 1 https://github.com/reggiechan74/cc-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.00142 | $0.05049 |
| Opus 5 | $0.00071 | $0.02524 |
| Sonnet 5 | $0.00028 | $0.01010 |
| Haiku 4.5 | $0.00014 | $0.00505 |
Grade A, and why
d3js 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create any D3.js data visualization quickly and correctly using D3 v7. This skill supports two workflows: direct implementation (default) for fast, professional output, and creative mode for artistic, philosophy-driven visualizations. Three output formats are available: standalone HTML, HTML + separate JS, and React components.
Default Configuration
These defaults apply to every visualization unless the user explicitly overrides them. The assumption is that the user will PDF, screenshot, or otherwise export the result for insertion into another document.
Layout: Single Screen, No Scrolling
Every visualization MUST fit entirely within a single browser viewport (100vh) with no scrolling required. This is non-negotiable.
Implementation rules:
- Set
html, body { height: 100vh; overflow: hidden; }on standalone HTML output - Use
body { display: flex; flex-direction: column; }withflex: 1on the chart container to fill available space - Use compact padding (
0.5rem–0.75rem), gaps (0.5rem), and font sizes - SVGs fill their containers via CSS (
width: 100%; height: 100%) rather than fixed pixel dimensions - Titles and labels use small but readable sizes (0.7–0.85rem for titles, 10–11px for axis text)
- When multiple charts share a page (dashboards), use CSS Grid with fractional rows (
1.2fr 1fr) andmin-height: 0on flex children to prevent overflow
Sizing: Responsive viewBox, Not Fixed Pixels
- Always use
viewBoxon SVGs — never set fixedwidth/heightattributes - Do not set inline
style("height", "auto")on SVGs — let CSS control sizing - Set
preserveAspectRatio="xMidYMid meet"on charts that need to maintain proportions (donut, pie, radial layouts)
Visual Style: Clean and Professional
- Color palette: Muted, purposeful colors from
d3.schemeTableau10or curated palettes. No rainbow, no random RGB. - Typography: System font stack (
-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif). No external font loads. - Background: Light gray page (
#f0f2f5), white chart panels with subtle box shadow - Axes: Light gray gridlines (
#f3f4f6), gray tick labels (#6b7280), no heavy borders - Margins: Generous enough for labels but not wasteful. Verify long labels (like "Natural Gas") are not truncated.
What ships with it
25 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.
- examples/react-component.tsx 5.0 KB
- examples/separate-js/chart.js 3.5 KB runs code
- examples/separate-js/index.html 1.3 KB
- examples/standalone.html 4.0 KB
- references/animation-interaction.md 10 KB
- references/chart-patterns.md 10.0 KB
- references/d3-api-quick-reference.md 13 KB
- references/geographic-patterns.md 8.2 KB
- references/hierarchy-network-patterns.md 11 KB
- templates/boilerplate.html 3.0 KB
- templates/gallery/analysis.json 15 KB
- templates/gallery/animation.json 30 KB
- templates/gallery/annotation.json 6.8 KB
- templates/gallery/areas.json 11 KB
- templates/gallery/bars.json 15 KB
- templates/gallery/dots.json 11 KB
- templates/gallery/essays.json 4.1 KB
- templates/gallery/fun.json 14 KB
- templates/gallery/hierarchies.json 14 KB
- templates/gallery/index.json 2.2 KB
- templates/gallery/interaction.json 10 KB
- templates/gallery/lines.json 17 KB
- templates/gallery/maps.json 21 KB
- templates/gallery/networks.json 14 KB
- templates/gallery/radial.json 6.3 KB
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 · 374 lines · 142 tokens per session scan A 035f3525b72f
d3js is a skill published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 142 tokens to every session and 5,049 once invoked, about $0.0007 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…