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-spec)<a href="https://agentmods.dev/skills/lavidrori0702/tableau-dashboard-creator-skill/tableau-spec"><img src="https://agentmods.dev/badge/skills/lavidrori0702/tableau-dashboard-creator-skill/tableau-spec/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/lavidrori0702/tableau-dashboard-creator-skill/tableau-spec"><img src="https://agentmods.dev/badge/skills/lavidrori0702/tableau-dashboard-creator-skill/tableau-spec.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.00204 | $0.02410 |
| Opus 5 | $0.00102 | $0.01205 |
| Sonnet 5 | $0.00041 | $0.00482 |
| Haiku 4.5 | $0.00020 | $0.00241 |
Grade A, and why
tableau-spec 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 4d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tableau-spec
Step 7 of 8, and non-skippable. It turns the approved mock.html into an
IMPLEMENTATION-SPEC.md that maps every mock element to a concrete Tableau construct,
so tableau-build builds from an explicit spec instead of guessing. It ends with a
coverage reconciliation — the mirror of the mock's checklist — proving every mock
element is mapped, and applies a simplest-primitive guard so the workbook uses the
simplest construct that does the job.
| Reads | Required: mock-version/<v_N>/mock.html (from mock) — the elements to map, tagged with data-plan-id; and DASHBOARD-PLAN.md (from plan) — the shared element/filter/interaction ids and the interaction intents (CONTRACT.md §6). |
| Writes | mock-version/<v_N>/IMPLEMENTATION-SPEC.md — a standalone deliverable copy (CONTRACT.md §4.3). |
| STATE.md update | Sets spec = approved; flips a downstream approved build step to stale on a re-run (CONTRACT.md §4.2). Does not touch current_version — only tableau-mock bumps it (§4.3). |
| Entry gate | Refuses to run until plan is resolved and DASHBOARD-PLAN.md exists, and mock is resolved and mock.html exists at current_version (CONTRACT.md §4.1). |
| Next step | tableau-build (or tableau-route to confirm). |
The mechanical guarantees — the entry gate, the coverage reconciliation (every mock
element mapped, nothing unmapped), the simplest-primitive guard (any advanced feature
carries a justification), the version bump, and the STATE.md transition — live in
spec.py (CLI) and reconcile.py (the reconciliation + guard core). Your job is the
judgment part: choosing the right, simplest Tableau construct for each element and
justifying any escalation. Run the script at the points below; do not hand-edit STATE.md.
The two conventions the reconciliation depends on
reconcile.py decides "mapped" and "laid out" mechanically, so the spec must carry a
single Element Mapping table and a Layout section (see
references/IMPLEMENTATION-SPEC-TEMPLATE.md):
What ships with it
3 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.
- 4d ago Changed 26d91fb1a4a3
- 10d ago First seen · 145 lines · 204 tokens per session scan A a87899837b97
tableau-spec is a skill published in the GitHub repository laviDrori0702/tableau-dashboard-creator-skill (21 stars, last pushed 5d ago), licensed MIT. It adds 204 tokens to every session and 2,410 once invoked, about $0.0010 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…
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".
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…