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/mingrath/wfdash/wf-chartingnpx skills add mingrath/wfdash --skill wf-chartinggit clone --depth 1 https://github.com/mingrath/wfdashWrote 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/mingrath/wfdash/wf-charting)<a href="https://agentmods.dev/skills/mingrath/wfdash/wf-charting"><img src="https://agentmods.dev/badge/skills/mingrath/wfdash/wf-charting.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.00133 | $0.00481 |
| Opus 5 | $0.00067 | $0.00241 |
| Sonnet 5 | $0.00027 | $0.00096 |
| Haiku 4.5 | $0.00013 | $0.00048 |
Grade A, and why
wf-charting 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 5d 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.
What it actually says
wf-charting
Standing amendments to how a wayfinder map is charted. They sit on top of however you already chart — nothing here replaces a step, and every rule states when it applies rather than where, so it holds whatever the charting procedure looks like today.
Read the rules
charting.md, beside this file, is the skill. Read it and follow it. This file only
points at it, and deliberately does not restate a single rule: there is exactly one
authored copy of the rules, and the same bytes are also injected into /wayfinder sessions
by the wayfinder-tools plugin's hooks. Two copies would drift, so there is only one.
When to read it
Whenever tickets are being made or wired — charting a fresh map, adding a ticket to an existing one, drawing a blocker between two of them, or filing the follow-up work a resolved question just unlocked. The rules fire at ticket creation, so reading them afterwards is reading them too late.
Why the marks matter
The hitl and afk labels are not bookkeeping. wfdash — the dashboard shipped from the
same repo as this skill, mingrath/wfdash — draws
them: the overview says per map whether an effort needs the dev present, and the map view
groups the frontier by them. A ticket created without one is invisible to both, and stays
that way, because unmarked is its own permanent value and never a synonym for afk.
What ships with it
1 file 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.
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.
- 5d ago First seen · 33 lines · 133 tokens per session scan A 9d33ea63f2ae
wf-charting is a skill published in the GitHub repository mingrath/wfdash (14 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 481 once invoked, about $0.0007 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-30.
Other skills, from other repositories
dashboard-design
Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after…
industry-chain
产业链下钻与不可替代性判定方法:以龙头为"需求入口"沿供应链逐层下钻(整机 / 龙头 → 部件 → 核心器件 → 材料 → 衬底与设备),用物理 / 材料约束(扩产周期、良率、认证周期、有无替代)当筛子找供给刚性的卡口;给每个标的贴不可替代性标签(techmoat / capacitymoat / both / 待补)并列证据;含"卡口越硬越贵"与预期差四问的校准。当任务涉及产业链位置、上下游、护城河、不可替代性、供给瓶颈、竞争格局时加载;单纯取数、估值计算、财报拆分等不涉及产业链结构的任务不要加载。只产出框架与证据表,不给投资动作建议。.
social-media-matrix
【模板: 社媒矩阵追踪 (Social Matrix Tracker)】 【意图】电影感、数据密集的多平台社媒看板。 【布局】.
live-dashboard
Notion 风团队仪表板, KPI + 7 日 sparkline + activity feed + 任务表.
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
catalyst-risk
催化剂与风险的反证式写法:每个强结论必须先找反证;催化剂按"兑现型 / 预期型 / 周期型"分类并要求可验证的数据时点;风险按技术路线断层、客户集中、产能过剩与价格战、周期顶、预期透支(假便宜 PEG)、一致预期下修、治理与流动性、数据源冲突分类;裁决点的标准写法(什么数据出来会改变判断 + 下一个公开数据时点);知识档案旧结论的反证处理。当任务涉及风险、反证、催化剂、裁决点、预期兑现、什么会推翻结论时加载;单纯取数、估值计算、财报拆分等不需要反证框架的任务不要加载。只产出框架、概率与裁决点,不给投资动作建议。.