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 tsmztech/claude-code-plugins/plugin install salesforce-cliWrote 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/tsmztech/claude-code-plugins/dashboard)<a href="https://agentmods.dev/skills/tsmztech/claude-code-plugins/dashboard"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/dashboard/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/tsmztech/claude-code-plugins/dashboard"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/dashboard.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.00166 | $0.03664 |
| Opus 5.5 | $0.00066 | $0.01466 |
| Sonnet 5.5 | $0.00033 | $0.00733 |
| Haiku 4.5 | $0.00017 | $0.00366 |
Grade A, and why
dashboard 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.
How it starts
The opening of the file, as written. The whole thing — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Dashboard Generator
Generate interactive HTML dashboards from Salesforce data. Produces a self-contained static HTML file with Chart.js charts, data tables, and KPI cards — no installation required.
Prerequisites
You must be authenticated to a Salesforce org before generating a dashboard. If not authenticated, run the authentication script first.
Authentication
If the user is not authenticated or gets an auth error, run the authentication script:
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --status
To authenticate interactively (opens browser):
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias>
Workflow
User describes dashboard
│
├── 1. Understand & Plan
│ ├── Interpret the user's request
│ ├── Plan: title, sections, chart types, data sources
│ └── DO NOT fetch data or generate anything yet
│
├── 2. Ask Style & Theme (MANDATORY — use AskUserQuestion)
│ ├── Present style options with descriptions
│ ├── Present theme options (light / dark / both with toggle)
│ └── WAIT for user to choose before proceeding
│
├── 3. Present Blueprint (MANDATORY — never skip)
│ ├── Show the dashboard blueprint with chosen style + theme:
│ │ ├── Dashboard title, style, theme
│ │ ├── Each section: type, title, chart type, data source description
│ │ └── Output filename
│ ├── Ask: "Does this look good, or would you like to change anything?"
│ └── WAIT for user confirmation before proceeding
│
├── 4. Fetch Data from Salesforce
│ ├── Run queries using salesforce-cli skills with --json flag
│ └── Collect all results
│
├── 5. Build Dashboard Config & Generate HTML
│ ├── Map query results → chart/table/KPI config
│ ├── Pipe JSON config via stdin to generate-dashboard.js
│ └── Open in browser
│
└── 6. Present to User
├── Show file path and size
└── Offer to adjust anything
Step 1: Understand & Plan
Interpret the user's request and design the dashboard layout. If the request is specific (e.g., "bar chart of opportunities by stage"), plan exactly that. If the request is vague (e.g., "show my pipeline"), infer a reasonable dashboard layout with multiple sections.
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.
- 2mo ago First seen · 359 lines · 166 tokens per session scan A 48854220b3b0
dashboard is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 166 tokens to every session and 3,664 once invoked, about $0.0007 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…