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/surfmind-space/awesome-surfmind/chart-explainernpx skills add surfmind-space/awesome-surfmind --skill chart-explainergit clone --depth 1 https://github.com/surfmind-space/awesome-surfmindWrote 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/surfmind-space/awesome-surfmind/chart-explainer)<a href="https://agentmods.dev/skills/surfmind-space/awesome-surfmind/chart-explainer"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/chart-explainer.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.00069 | $0.00622 |
| Opus 5 | $0.00034 | $0.00311 |
| Sonnet 5 | $0.00014 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
chart-explainer 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chart Explainer
Explain the chart, graph, or plot the way a careful analyst would — what the axes measure, the trend and its size, the outliers, and the one takeaway that answers the user's likely question. Work only from what's visible in the chart, the user's selected text, or tool results; don't infer exact numbers you can't read off the chart, and don't treat a correlation as a cause.
- Identify the chart type, title, axes, units, time period, categories, legend, and any visible data limits or gaps.
- Explain the trend, level, notable changes, outliers, comparisons, and uncertainty — with sizes when the chart shows them.
- Connect the visual takeaway to the user's likely question or decision.
- Flag missing context (sample size, baseline, source, scale tricks) needed before acting on the chart.
Return concise headings and include these sections when they fit: What the chart shows, Main takeaway, Notable details, Caveats, Questions to verify. Preserve important names, numbers, links, dates, and currencies. Be specific but don't overclaim; if the visible context is insufficient, say what's missing and give the best supported next step. Respond in the same language as the user's request.
Example
Chart (a line chart titled "Monthly active users"):
X-axis: Jan–Dec 2025. Y-axis: MAU in thousands, starting at 80, not 0. One line rising from ~120k in Jan to ~180k in Dec, with a dip to ~110k in July. No source or sample note.
Explanation:
What the chart shows: Monthly active users across 2025, climbing from ~120k to ~180k — about a 50% gain over the year.
Main takeaway: Steady growth, but the trend isn't smooth; one sharp mid-year drop interrupts it.
Notable details: July dips to ~110k — the lone outlier, roughly a 40% fall before recovering. The Y-axis starts at 80k, not 0, which visually exaggerates the slope.
Caveats: No source, definition of "active," or sample size is shown, so the absolute numbers can't be verified. The truncated axis overstates the gain at a glance.
Questions to verify: What caused the July drop (outage, seasonality, tracking change)? How is "active" defined, and is the data first-party?
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 · 40 lines · 69 tokens per session scan A 1f2e0387c67e
chart-explainer is a skill published in the GitHub repository surfmind-space/awesome-surfmind (5 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 622 once invoked, about $0.0003 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
cs-master
Expert computer scientist for algorithms, complexity analysis, and distributed systems.
uiux-master
UI/UX expert for design systems, accessibility, and avoiding generic AI-generated design patterns.
c-master
C programming expert for memory management, systems programming, and performance optimization.
data-science
ML engineering expert for feature engineering, model debugging, and production pipelines.
go-master
Go expert for goroutines, channels, microservices, and concurrent patterns.
network-devops
Network performance expert for latency optimization, packet analysis, and infrastructure tuning.