infographic

infographic is a skill for Claude Code, Codex from magnus919/agent-skills. It costs 81 tokens per session (1,125 once invoked), scanned A, original, MIT.

A procedure for designing infographics: visual explanations that combine text, images, diagrams, and data. It helps structure information so a particular audience can understand, compare, choose, or act.

In plain words
What is it for?
Use it to create or improve infographics, visual explainers, comparison posters, process graphics, and data stories.
Why use it?
It reduces the risk of making a graphic that looks finished but is hard to read or communicates incorrect relationships. It also clarifies the audience, viewing context, language, and accessibility needs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create or improve infographics, visual explainers, comparison posters, process graphics, and data stories.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/magnus919/agent-skills/infographic
Install

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.

Any agent
npx skills add magnus919/agent-skills --skill infographic
Clone the repo
git clone --depth 1 https://github.com/magnus919/agent-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin infographic — /plugin install infographic after adding the marketplace above.

Wrote 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.

agentmods badge for infographic

README.md
[![agentmods](https://agentmods.dev/badge/skills/magnus919/agent-skills/infographic/github.svg)](https://agentmods.dev/skills/magnus919/agent-skills/infographic)
Your own site
<a href="https://agentmods.dev/skills/magnus919/agent-skills/infographic"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/infographic/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.

agentmods 80×15 button for infographic

Your own site · 80×15
<a href="https://agentmods.dev/skills/magnus919/agent-skills/infographic"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/infographic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,125 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.01125
Opus 5.5 $0.00032 $0.00450
Sonnet 5.5 $0.00016 $0.00225
Haiku 4.5 $0.00008 $0.00112

Measured yesterday against content hash 14d55443c2f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

infographic 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 yesterday.

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.

infographic/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Infographic

Produce a visual explanation that helps its intended reader understand, compare, choose, or act. A beautiful image with incorrect relationships or unreadable content is unfinished. This skill supplies judgment and design specifications; it does not install a renderer or confer access to an image-generation service.

When not to use

Use brand-designer for identity systems, data-scientist for statistical inference, documents for office/PDF production, and color-management for ICC/profile operations. These optional companion skills can support an infographic without replacing its editorial decisions. If a companion is not installed, use available tool guidance; do not assume a sibling path or capability exists. For decorative artwork alone, use the available image tool's own workflow.

Workflow

  1. Frame the communication contract. Establish who will read it, what they already know, and what they should understand or do afterward. Identify the real viewing context, dimensions, language, accessibility needs, and requested deliverables. Infer low-risk defaults and state them briefly; ask only for missing information that materially changes correctness or usefulness. Scale the process to the request: a small family guide does not need a long brief. Use the brief for complex work.
  2. Ground the message. Read evidence and editorial judgment for factual, quantitative, persuasive, or source-poor requests. Write the principal takeaway and the few supporting claims before decorating. Preserve material limitations beside affected claims. Do not invent statistics, citations, or causal relationships. A request for impressive numbers does not supply evidence. If sources are missing, research when available or produce a clearly qualitative/illustrative version and explain the limitation.
  3. Choose the information structure. Read layouts and encodings when composing or revising. Match the reader's task and real relationships to a comparison, sequence, timeline, mechanism, hierarchy, geography, data story, or reference arrangement. Sketch the reading order and focal point. Arrows, areas, containers, proximity, and numbering all make claims; use them deliberately.
  4. Choose a visual language separately. Read style recipes when a style is requested or needs choosing. Select a coherent direction appropriate to the reader, subject, medium, and supplied brand constraints. Offer a few genuinely different directions only when the choice is consequential; otherwise choose and explain one. A timeline can be a spare editorial graphic, a playful cut-paper story, or a technical plate without changing chronology.
  5. Execute with real capabilities. Read production before rendering. Check available tools, fonts, export formats, and inspection routes. Use deterministic geometry and typesetting for exact numerical charts and dense required copy. Use image generation for expressive conceptual imagery where available; hybrid assembly is valid. Follow the active image tool's rules. A text prompt is a production specification, not a rendered artifact. Do not claim execution or file formats that were not produced.
  6. Inspect and improve the actual export. Read review and polish before delivery. Verify evidence, geometry, visual semantics, hierarchy, actual-size legibility, accessibility, and export integrity separately. Repair content and structure before cosmetic details. Re-render after consequential edits; check the final file, not only the source or previous preview.
  7. Deliver what exists. Provide the requested visual, editable source when available, an accessible text equivalent, and traceable source notes. Briefly state meaningful limitations and what was tested. If rendering is unavailable, deliver a usable specification and exact copy, explicitly marked unrendered. Stop when the artifact meets its communication contract and review gates, or when a specific missing capability/source prevents completion. After two non-improving repair attempts on the same defect, change the approach or report the blocker rather than cycling indefinitely.

Read the full file on GitHub · 91 lines

Files

What ships with it

11 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.

Changes

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.

  1. yesterday First seen · 91 lines · 81 tokens per session scan A 14d55443c2f8

Subscribe to this mod's changes

infographic is a skill published in the GitHub repository magnus919/agent-skills (133 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 1,125 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-10-17.