Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add laviDrori0702/tableau-dashboard-creator-skill/plugin install tableau-dashboard-pluginWrote 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/lavidrori0702/tableau-dashboard-creator-skill/tableau-data)<a href="https://agentmods.dev/skills/lavidrori0702/tableau-dashboard-creator-skill/tableau-data"><img src="https://agentmods.dev/badge/skills/lavidrori0702/tableau-dashboard-creator-skill/tableau-data.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.1 | $0.00134 | $0.02553 |
| Opus 5 | $0.00067 | $0.01277 |
| Sonnet 5 | $0.00027 | $0.00511 |
| Haiku 4.5 | $0.00013 | $0.00255 |
Grade A, and why
tableau-data 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 3d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tableau-data
Step 3 of 8, and non-skippable. It turns the analyst's data into DATA-MODEL.md
— the documented field names and types that tableau-mock and tableau-build
build against. The CSVs under data/ are the single source of truth for those field
names, so this step also validates that the documented names match the real CSV
headers exactly before approving.
| Reads | The data: production data/*.csv (preferred) or the scaffold/sample-data/*.csv demo fallback. For the published-ds route, the inputs datasources.json + .env (the latter discovered by walking up — nearest wins). None is a required read — data has no producer-gated inputs (CONTRACT.md §1). |
| Writes | DATA-MODEL.md at the project root (latest approved truth; overwritten in place). The CSVs themselves are analyst-provided in data/ (or the demo scaffold/sample-data/). |
| STATE.md update | Sets data = approved; flips every downstream approved step to stale on a re-run (CONTRACT.md §4.2). |
| Entry gate | Refuses to run until init is approved in STATE.md (CONTRACT.md §4.1). |
| Next step | tableau-brand (or tableau-plan, or tableau-route to confirm). |
The two acquisition routes (and no third)
There are exactly two ways to get the mimicking CSVs (CONTRACT.md §3.2). There is
no synthesized/random-data path — when no real data exists, the floor is the
clearly-labelled scaffold/sample-data/ demo, never invented rows.
- Route 1 —
data_mode: csv(default, zero-credential). The analyst drops CSV file(s) indata/. Each CSV is one data source.profile→ enrich →commit. - Route 2 —
data_mode: published-ds(VizQL Data Service). The analyst lists published sources indatasources.json(one entry each:ds_name+project_name) and supplies a Tableau connection in.env.pullsigns in with the Personal Access Token and samples each source through the VDS —read-metadata(authoritative field names/types/descriptions) thenquery-datasource(a capped row sample) — writing onedata/<slug>.csvper source plusDATA-MODEL.md. Then enrich →commit, exactly as Route 1. Fires only whendata/has no production CSVs (real CSVs always win).
What ships with it
5 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.
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.
- 3d ago Changed 1ffa04870c23
- 8d ago First seen · 162 lines · 134 tokens per session scan A c47643c215a1
tableau-data is a skill published in the GitHub repository laviDrori0702/tableau-dashboard-creator-skill (21 stars, last pushed 4d ago), licensed MIT. It adds 134 tokens to every session and 2,553 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
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
agent-ready-cloudflare
Audit and improve website readiness for AI agents using the Cloudflare "Is It Agent Ready?" scanner (isitagentready.com). Covers scanning via API, interpreting results, generating implementation prompts, and fixing every check. Use when the user mentions "agent ready", "isitagentready", "AI agent scan", "agent…
aidlc-master
Runs the AWS AI-DLC (AI-Driven Development Life Cycle) methodology end to end: an adaptive three-phase workflow (Inception → Construction → Operations) with human approval gates, a full audit trail, and all artifacts in aidlc-docs/. Use when the user says "Using AI-DLC", "AI-DLC", "AIDLC", "aidlc-master", or asks for…
slop-eval
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…
ralph-loop-kiro-specs
Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user…
security-specialist
Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking. Activate when the user says "security scan", "audit this repo", "review this PR for security", "threat model", "triage vulnerabilities", "fix this vuln", or "track findings".