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 andisab/swe-marketplace --skill chartwaregit clone --depth 1 https://github.com/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/chartware)<a href="https://agentmods.dev/skills/andisab/swe-marketplace/chartware"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/chartware/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/andisab/swe-marketplace/chartware"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/chartware.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00217 | $0.02334 |
| Opus 5.5 | $0.00087 | $0.00934 |
| Sonnet 5.5 | $0.00043 | $0.00467 |
| Haiku 4.5 | $0.00022 | $0.00233 |
Grade A, and why
chartware 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 today.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chartware — Diagrams & Data Charts (Mermaid · SVG · draw.io)
One skill, three media, one visual identity. Diagrams and charts resolve their colors from the same brand registry as slideware decks and knowledgebase sites.
Choosing the medium
An explicit user request always wins ("as a mermaid diagram", "in draw.io", "as SVG"). Otherwise pick by fit — and say which medium you chose and why:
| Medium | Choose when | Strengths | Limits |
|---|---|---|---|
| Mermaid | The diagram lives in markdown, a knowledgebase page, or an artifact; speed and text-maintainability matter more than exact layout | Renders natively in most targets; diffable; cheap to iterate | Auto-layout only — no pixel control; weak for data charts |
| SVG | Data charts (default medium for them); polished figures embedded in HTML deliverables; standalone .svg files; print |
Total control; themes with the page (light/dark); no dependencies | Hand-computed layout; not end-user editable |
| draw.io | The user will open/edit/maintain the diagram; large layered reference architectures; a .drawio artifact is the deliverable |
Real editor round-trip; the full curated style catalog | Needs the drawio MCP; heavier iteration loop |
Rules of thumb: flowchart in a README → Mermaid. Revenue chart in a report page → SVG. Enterprise reference architecture the client will maintain → draw.io. A diagram embedded in a knowledgebase/slideware deliverable → Mermaid if its auto-layout suffices, SVG when the layout must be exact.
Brand resolution (all media)
If the user names a brand or style ("in the AAB style", "AcmeCorp-branded"), resolve it from the registry — $KNOWLEDGEWARE_BRANDS_DIR/<name>.md first (if that env var is set — the user's own brands directory), then styles/brands/<name>.md (plugin root — two directories above this skill), falling through to styles/<name>.md for the generic defaults — and substitute its palette/typography per the brandware skill's references/consumer-mappings.md §chartware. The mapping is deliberately understated — surface fills with categorical strokes, brand accent in at most two roles, low-saturation tints; a branded diagram should read as the brand's document, not a poster of its colors. For data charts (bars, lines, KPIs) follow brandware's references/chart-styling.md. If the brand isn't installed, use the defaults below and say so. When the user names no brand at all, check the DEFAULT marker (a one-line file naming a registry entry; $KNOWLEDGEWARE_BRANDS_DIR/DEFAULT wins over styles/brands/DEFAULT) and apply that identity if it resolves, telling the user; otherwise use each medium's default styling.
What ships with it
14 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.
- references/drawio-layout.md 12 KB
- references/styles.md 28 KB
- references/svg-charts.md 18 KB
- templates/architecture.xml 10 KB
- templates/flow.xml 5.1 KB
- templates/orgchart.xml 5.7 KB
- templates/sequence.xml 5.4 KB
- templates/svg/bar-grouped.svg 5.4 KB
- templates/svg/bar-horizontal.svg 4.7 KB
- templates/svg/diagram-flow.svg 7.3 KB
- templates/svg/donut.svg 4.3 KB
- templates/svg/kpi-tile.svg 3.9 KB
- templates/svg/line-area.svg 6.1 KB
- templates/svg/scatter.svg 5.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.
- today First seen · 100 lines · 217 tokens per session scan A 5ae62bcfa845
chartware is a skill published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed today), licensed MIT. It adds 217 tokens to every session and 2,334 once invoked, about $0.0009 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-10-17.
Other skills, from other repositories
ccc-brainstorm
Design-first ideation gate: three parallel agents propose a simple, a scalable and a user-delight approach, rendered as a tradeoff matrix, then you pick a direction. No code is written. Use when the user asks how to build X, which approach to take, is torn between options, or types $ccc-brainstorm.
matilha-design
Use when user is making UX, UI, or visual-design decisions in any phase — guides via core design heuristics and delegates to matilha-design-pack or matilha-ux-pack if installed.
accessibility-compliance-accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
ux-design
Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.