port-dashboard-plugins

port-dashboard-plugins is a skill for Claude Code from port-labs/port-skills. It costs 192 tokens per session (5,043 once invoked), scanned A, original, MIT.

A guide to building custom Port dashboard widgets as small React and TypeScript applications that run inside an isolated browser frame. Port is a platform for dashboards and connected software data.

In plain words
What is it for?
Use it to build, compile, and upload custom widgets that read Port data and appear on dashboards or object pages.
Why use it?
It explains how the widget and dashboard exchange data safely and how to avoid common blank-widget problems.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions Codex.

Part of the port-skills plugin — 10 skills, 1 command, 2 MCP servers shipped together

Good fit Use it to build, compile, and upload custom widgets that read Port data and appear on dashboards or object pages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/port-labs/port-skills/port-dashboard-plugins
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 port-labs/port-skills --skill port-dashboard-plugins
Clone the repo
git clone --depth 1 https://github.com/port-labs/port-skills

Made for: Claude Code.

Or install port-skills, the plugin that ships this one along with the rest of its 10 skills, 1 command, 2 MCP servers.

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.

agentmods badge for port-dashboard-plugins

README.md
[![agentmods](https://agentmods.dev/badge/skills/port-labs/port-skills/port-dashboard-plugins/github.svg)](https://agentmods.dev/skills/port-labs/port-skills/port-dashboard-plugins)
Your own site
<a href="https://agentmods.dev/skills/port-labs/port-skills/port-dashboard-plugins"><img src="https://agentmods.dev/badge/skills/port-labs/port-skills/port-dashboard-plugins/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.

agentmods 80×15 button for port-dashboard-plugins

Your own site · 80×15
<a href="https://agentmods.dev/skills/port-labs/port-skills/port-dashboard-plugins"><img src="https://agentmods.dev/badge/skills/port-labs/port-skills/port-dashboard-plugins.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 192 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,043 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00192 $0.05043
Opus 5 $0.00096 $0.02521
Sonnet 5 $0.00038 $0.01009
Haiku 4.5 $0.00019 $0.00504

Measured 11d ago against content hash cddeabf062b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

port-dashboard-plugins 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 11d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (assets/template-config.ts, assets/template-resolveHostEntity.ts, assets/template-types.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/port-dashboards/port-dashboard-plugins/SKILL.md · 367 lines

How it starts

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

Port custom plugin widgets

A Port custom plugin is a small React/TypeScript app that compiles to a single self-contained dist/index.html and runs inside an <iframe> on a dashboard or entity page. Port and the plugin talk over window.postMessage only: the plugin never gets direct DOM access to the host page, and the host never runs the plugin's code outside the iframe sandbox. This skill is reference-only: static knowledge of the SDK, the host bridge protocol, and the upload CLI, drawn from @port-labs/plugins-sdk, @port-labs/port-plugins-cli, and Port's plugins docs. It doesn't need a live Port account or MCP server to scaffold and build a plugin, only a real account to upload and view it.

Out of scope: Port's built-in dashboard widget types (tables, number charts, pie charts, and the rest) need no custom code at all, that's the parent port-dashboards skill. Ocean integrations (data ingestion into the context lake) are a different system with a different SDK. Blueprint and property modeling with no widget implementation is owned by port-blueprints; this skill only covers how a plugin reads that schema at design time and at runtime.

Skill class

Reference skill: the SDK contract, hooks-order rule, and webpack safety patches below are static platform rules, not something a live account changes. Context lake design (which blueprint or relation a plugin should read) benefits from the Port MCP server (list_blueprints, upsert_blueprint) as an optional, design-time-only enhancement, never call MCP from inside plugin runtime code. Without MCP, use the Port UI's blueprint builder, or GET /v1/blueprints / GET /v1/blueprints/{identifier} directly.

Prerequisites

  • Go over the port-getting-started skill first if this is your first time working with Port.
  • Node.js >= 20.
  • A Port account with permission to add custom plugins (admin, in most organizations). Search search_port_knowledge_sources for anything this skill doesn't cover.
  • @port-labs/port-plugins-cli for uploading the built plugin (npm install -g @port-labs/port-plugins-cli or npx), with a client_id/client_secret pair from ... menu > Credentials in the Port app.
  • Read access to the target blueprint's schema, from the Port UI, the API, or MCP if connected, before writing upload-params.json.

Read the full file on GitHub · 367 lines

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.

  1. 11d ago First seen · 367 lines · 192 tokens per session scan A cddeabf062b0

Subscribe to this mod's changes

port-dashboard-plugins is a skill published in the GitHub repository port-labs/port-skills (3 stars, last pushed 9d ago), licensed MIT. It adds 192 tokens to every session and 5,043 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-31.

Related

Other skills, from other repositories

effect-best-practices

Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.

betalyra/effect-skills · 45 tokens

effector-ecosystem

Use when designing, reviewing, generating, or refactoring React applications built with Effector, effector-react, Farfetched, Atomic Router, @effector/next, patronum, effector-storage, forms, i18n, testing, and related Effector ecosystem tooling. For Feature-Sliced Design project structure and placement decisions, use…

demark-pro/skills · 83 tokens

react-bits

Use when adding an animated UI component, text effect, cursor/hover effect, or WebGL/canvas background to a React project via React Bits (reactbits.dev) — or when asked to recall/write a React Bits component's code, props, or install steps from memory instead of fetching it.

Philotheephilix/reactbits.dev-skill · 64 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

material-ui-tailwind

Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.

mui/material-ui · 67 tokens

fuzzy-ranking

Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics. Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring.

TanStack/table · 62 tokens