The implementation stage that turns approved writing, data findings and visual specifications into a final HTML page. It follows those instructions and does not make editorial or visual decisions.

Use it to build the final index.html from the project files. It handles page structure, displayed text, visual components and the supplied chart data.

It keeps the finished page faithful to the approved story and design instead of changing the meaning during coding. It also connects charts to their source data through traceability attributes.

programmer — Skill for Claude Code by QinghongLin/data2story-skill

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 QinghongLin/data2story-skill --skill programmer

Clone the repo

git clone --depth 1 https://github.com/QinghongLin/data2story-skill

Made for: Claude Code.

Or install data2story-pro, the plugin that ships this one along with the rest of its 25 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/qinghonglin/data2story-skill/programmer/github.svg)](https://agentmods.dev/skills/qinghonglin/data2story-skill/programmer)

Your own site

<a href="https://agentmods.dev/skills/qinghonglin/data2story-skill/programmer"><img src="https://agentmods.dev/badge/skills/qinghonglin/data2story-skill/programmer/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/qinghonglin/data2story-skill/programmer"><img src="https://agentmods.dev/badge/skills/qinghonglin/data2story-skill/programmer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,659 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00051	$0.06659
Opus 5.5	$0.00020	$0.02664
Sonnet 5.5	$0.00010	$0.01332
Haiku 4.5	$0.00005	$0.00666

Measured 2mo ago against content hash 0cdbc9f74ebe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

programmer 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 2mo 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.

skills/data2story-pro/programmer/SKILL.md · 126 lines

How it starts

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

Programmer

Your job is faithful implementation. Build exactly what the Editor wrote and the Designer specified. You do not make editorial decisions. You do not make visual decisions. You make them real.

Setup

PROJECT_DIR = first argument
Read these files before writing any code:
- PROJECT_DIR/editor.md — verbatim prose for the blog
- PROJECT_DIR/editor.json — section structure with edt_xx IDs
- PROJECT_DIR/analyst.json — data findings with ana_xx IDs and data_tables
- PROJECT_DIR/designer.json — visual specs with des_xx IDs
- PROJECT_DIR/copywriter.json (if present) — the Copywriter's re-titled STRINGS: masthead{headline,standfirst,kicker} + items{edt_xx:{title}, des_xx:{caption,subtitle}}. Render these verbatim as the page H1 / standfirst / kicker, the section titles, and the <figcaption>s (see Step 2). The Copywriter reuses the existing edt_/des_ ids and adds none, so this changes only the displayed LABELS — no data-* tag, no number, no provenance changes.
- PROJECT_DIR/hero.json (if present) — the Hero role's animated-cover spec + assets (assets/teaser.webm/_web.mp4/.jpg); reuses data-des="des_hero_video". Build the hero per the contract in the Teaser bullet (Step 2).
Output: PROJECT_DIR/index.html

You do NOT have access to raw data files. Chart data comes from analyst.json data_tables. For an interactive explorable you MAY inline the Analyst's client_model (params + a pure-JS recompute function, from analyst.json / code/) so the reader can re-run the model in the browser — that is analyst-sourced, not raw-file access.

Step 0: Learn from Past Mistakes

Consult the curated pitfalls log — do NOT reintroduce these known mistakes. Before writing any code, read ../../frontend-design-pro/references/pitfalls.json — the 错题本 of real bugs from past runs (invisible width:container charts, breakouts that won't center, SVGs overflowing their card, starved card bars, autoplay/self-host audio traps, IP-risky proprietary numbers). Apply each entry's fix up front. For the cinematic flagship pattern specifically, study the worked exemplar ../../frontend-design-pro/references/exemplars/cinematic_flagship.md before laying out the page.

Read the full file on GitHub · 126 lines

Files

What ships with it

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

2mo ago First seen · 126 lines · 51 tokens per session scan A 0cdbc9f74ebe

Subscribe to this mod's changes

programmer is a skill published in the GitHub repository QinghongLin/data2story-skill (161 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 6,659 once invoked, about $0.0002 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-08-30.

Frontend agent-skills data-journalists data-science

programmer next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
programmerQinghongLin/data2story-skill	Skill	161	4mo ago	MIT	A	51	Claude Code
chdb-sqlchdb-io/chdb	Skill	2.9k	6d ago	Apache-2.0	A	214	Claude Code, Codex
waxchristopherkarani/Wax	Skill	806	2d ago	Apache-2.0	A	76	Codex
wax-memory-maintenancechristopherkarani/Wax	Skill	806	2d ago	Apache-2.0	A	18	Claude Code, Codex
alterlab-timesfmAlterLab-IEU/AlterLab-Academic-Skills	Skill	85	yesterday	MIT	A	150	Claude Code
alterlab-cobrapyAlterLab-IEU/AlterLab-Academic-Skills	Skill	85	yesterday	MIT	A	91	Claude Code
alterlab-molecular-dynamicsAlterLab-IEU/AlterLab-Academic-Skills	Skill	85	yesterday	MIT	A	98	Claude Code