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 skills add tam159/next-role --skill chartsgit clone --depth 1 https://github.com/tam159/next-roleWrote 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/tam159/next-role/charts)<a href="https://agentmods.dev/skills/tam159/next-role/charts"><img src="https://agentmods.dev/badge/skills/tam159/next-role/charts/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tam159/next-role/charts"><img src="https://agentmods.dev/badge/skills/tam159/next-role/charts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.01145 |
| Opus 5.5 | $0.00028 | $0.00458 |
| Sonnet 5.5 | $0.00014 | $0.00229 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
charts 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Charts
create_chart runs your SQL, draws the result, and saves it to the
conversation. Charts persist: reopening the thread later still shows them.
Chart or not
Draw when the shape is the answer: a trend over time, a comparison across categories, a distribution, a two-dimensional pattern.
Do not draw when a sentence is the answer. One number is a sentence, or a kpi
if it deserves emphasis. Three rows are a table. A chart of three bars is
noise.
Choosing a kind
| Question shape | Kind | Mapping |
|---|---|---|
| How did X move over time? | line |
x = date, y = measure |
| Same, several measures or groups | line |
plus series, or a list of y |
| Same, composition over time | area with stacked=True |
x, y, series |
| How do categories compare? | bar |
x = category, y = measure |
| Composition within each category | bar with stacked=True |
plus series |
| Share of a whole, few slices | pie |
x = labels, y = values |
| How is a value distributed? | histogram |
x = the column to bin |
| Two dimensions against one value | heatmap |
x = columns, series = rows, y = value |
| Exact figures matter | table |
no mapping |
| One headline number | kpi |
y = value, x = optional label |
Use pie only up to about six slices; beyond that a bar chart reads better.
Getting it right
- Aggregate in SQL. The tool refuses more than a few thousand rows, and a chart of raw rows is unreadable anyway.
- Order the query the way the chart should read: by date for a trend, by value descending for a ranked bar chart.
- Give every chart a title that states the finding, not the mechanism: "LLM cost per day by model", not "Query results".
- Put the caveat in
description. Cost charts should say the figures are list price estimates; anything over message dates should say the timestamps are capture times. - Set
y_format:currencyfor dollars,percentfor rates (pass the fraction, not 0-100),duration_sfor seconds. - Reuse a
slugto replace a chart you already made rather than accumulating near-duplicates.
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.
- 1mo ago First seen · 114 lines · 70 tokens per session scan A 2a14262251ef
charts is a skill published in the GitHub repository tam159/next-role (62 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,145 once invoked, about $0.0003 per session on Opus 5.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-09-06.
Other skills, from other repositories
ai-dev-jobs-mcp-v2
AI Dev Jobs MCP workflow skill. Use this skill when the user needs Search 8,400+ AI and ML jobs across 489 companies, inspect listings and employers, match roles, and view salary and market stats via AI Dev Jobs MCP and the operator should preserve the upstream workflow, copied support files, and provenance before…
ai-dev-jobs-mcp
AI Dev Jobs MCP workflow skill. Use this skill when the user needs Search 8,400+ AI and ML jobs across 489 companies, inspect listings and employers, match roles, and view salary and market stats via AI Dev Jobs MCP and the operator should preserve the upstream workflow, copied support files, and provenance before…
openspec-verify-change
Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
cli-resilience
Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.