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/thesecondfox/skill/bio-data-visualization-multipanel-figuresnpx skills add thesecondfox/skill --skill bio-data-visualization-multipanel-figuresgit clone --depth 1 https://github.com/thesecondfox/skillWrote 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/skills/thesecondfox/skill/bio-data-visualization-multipanel-figures)<a href="https://agentmods.dev/skills/thesecondfox/skill/bio-data-visualization-multipanel-figures"><img src="https://agentmods.dev/badge/skills/thesecondfox/skill/bio-data-visualization-multipanel-figures.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.00048 | $0.01942 |
| Opus 5 | $0.00024 | $0.00971 |
| Sonnet 5 | $0.00010 | $0.00388 |
| Haiku 4.5 | $0.00005 | $0.00194 |
Grade A, and why
bio-data-visualization-multipanel-figures 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 4d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Compatibility
Reference examples tested with: ggplot2 3.5+, matplotlib 3.8+
Before using code patterns, verify installed versions match. If versions differ:
- Python:
pip show <package>thenhelp(module.function)to check signatures - R:
packageVersion('<pkg>')then?function_nameto verify parameters
If code throws ImportError, AttributeError, or TypeError, introspect the installed package and adapt the example to match the actual API rather than retrying.
Multi-Panel Figure Assembly
"Combine multiple plots into one figure" → Arrange subplots into a publication-ready multi-panel layout with shared legends and consistent sizing.
- R:
patchwork::wrap_plots(),cowplot::plot_grid() - Python:
matplotlib.pyplot.subplots(),fig.add_subplot()
patchwork Basics
library(patchwork)
p1 <- ggplot(df, aes(x, y)) + geom_point()
p2 <- ggplot(df, aes(group, value)) + geom_boxplot()
p3 <- ggplot(df, aes(x)) + geom_histogram()
# Horizontal
p1 + p2 + p3
# Vertical
p1 / p2 / p3
# Mixed layouts
(p1 | p2) / p3
(p1 + p2) / (p3 + p4)
Panel Labels
# Automatic labels
(p1 + p2 + p3) + plot_annotation(tag_levels = 'A')
# Custom labels
(p1 + p2 + p3) + plot_annotation(tag_levels = list(c('A', 'B', 'C')))
# Label styling
(p1 + p2) + plot_annotation(
tag_levels = 'A',
tag_prefix = '(',
tag_suffix = ')',
theme = theme(plot.tag = element_text(face = 'bold', size = 14))
)
Layout Control
# Width ratios
p1 + p2 + plot_layout(widths = c(2, 1))
# Height ratios
p1 / p2 + plot_layout(heights = c(1, 2))
# Complex grid
layout <- "
AAB
AAB
CCC
"
p1 + p2 + p3 + plot_layout(design = layout)
# Fixed dimensions
p1 + p2 + plot_layout(widths = unit(c(5, 3), 'cm'))
Shared Legends
# Collect legends
(p1 + p2 + p3) + plot_layout(guides = 'collect')
# Position at bottom
(p1 + p2) + plot_layout(guides = 'collect') &
theme(legend.position = 'bottom')
# Keep individual legends
(p1 + p2) + plot_layout(guides = 'keep')
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.
- 4d ago First seen · 274 lines · 48 tokens per session scan A a58bd8a434cf
bio-data-visualization-multipanel-figures is a skill published in the GitHub repository thesecondfox/skill (3 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 1,942 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-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…