PortalJS is a framework for building data portals that present searchable datasets through a home page, catalog, and dataset showcase. It is for teams that want to choose a data backend, scaffold a Next.js portal, load CSV or JSON data, connect services such as CKAN, and deploy the result. The catalogue entries are agent commands, skills, instructions, and a plugin that guide portal creation and data loading.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/datopian/portaljsnpx agentmods add skills/datopian/portaljs/portaljs-new-portalWrote 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/datopian/portaljs/portaljs-new-portal)<a href="https://agentmods.dev/skills/datopian/portaljs/portaljs-new-portal"><img src="https://agentmods.dev/badge/skills/datopian/portaljs/portaljs-new-portal/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/datopian/portaljs/portaljs-new-portal"><img src="https://agentmods.dev/badge/skills/datopian/portaljs/portaljs-new-portal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 62 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 72 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00046 | $0.01492 |
| Opus 5 | $0.00023 | $0.00746 |
| Sonnet 5 | $0.00009 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
portaljs-new-portal 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 12d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PortalJS — New Portal
Overview
Scaffold a production-ready PortalJS data portal from a brief. The skill is
interactive: if the brief is thin it interviews the user in three short rounds
(mapped to the template's three surfaces — Home, Catalog, Showcase), echoes a brief
back for confirmation, then copies examples/portaljs-catalog (locally or via a
remote tiged fetch), substitutes placeholder tokens, sets the namespace mode, seeds
any datasets named in the interview, installs dependencies, and verifies the scaffold
with a type check.
Prerequisites
- Node.js >=22 and npm available on
PATH. - Network access, unless a current local checkout of the portaljs repo is available (the resolver defaults to a remote fetch of the template).
- A destination directory name that does not already contain files (or user consent to overwrite one that does).
Instructions
The canonical, full step-by-step workflow is
.claude/commands/portaljs-new-portal.md —
the single source of truth. Read and follow it when executing. Summary:
- Interview the user in up to three rounds — Home/basics, Catalog & discovery
(datasets, namespace mode
themevsowner), Showcase/views — skipping any round already answered by the input brief. Accept "use defaults" at any point. - Confirm a short brief (name, slug, description, namespace, datasets, views) before building.
- Resolve the template source: prefer a remote
tigedfetch ofexamples/portaljs-catalogatmain(orPORTALJS_TEMPLATE_REF); use a local checkout only when it is current (haspages/[owner]/[slug].tsx) and the destination is outside that repo. - Materialize the template into
./PROJECT_SLUG, asking first if the destination already exists and is non-empty. - Substitute
__PROJECT_NAME__,__PROJECT_SLUG__,__DESCRIPTION__tokens across all files withperl -pi, escaping/,\, and&in the values. - Set
NAMESPACE_TYPE('theme'or'owner') inlib/datasets.tsper the interview. - Seed datasets captured in Round 2 (via
/portaljs-add-datasetor by hand), or cleardatasets.jsonto[]if none were named. - Run
npm installinside the scaffolded portal. - Verify with
npx tsc --noEmit(nevernext buildhere — it would corrupt a running dev server's.next/directory). - Report the scaffolded routes, namespace mode, and next steps.
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.
- 12d ago First seen · 120 lines · 46 tokens per session scan A 37e27cff6f7e
portaljs-new-portal is a skill published in the GitHub repository datopian/portaljs (2,350 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 1,492 once invoked, about $0.0002 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
export-component-to-other-repo
Port a component from nextjs-css-agent-components into a different repo without losing the design-system precision. Use when the user says "copy this component to ", "lift Button into ", "bring the Thin layout over", or otherwise wants a faithful transplant of one or more components from this codebase. Carries over…
build-app-page
Construct a new app page from scratch using this repo's component system. Use when the user says "build a new page for X", "create a settings page", "add a dashboard for Y", "scaffold an app screen", or otherwise wants a Next.js page assembled from the project's elements/components/patterns. Produces a route under…
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
replace-me-skill
Load when copying this directory to bootstrap a new OmicsClaw v2 skill (rename, fill in skill.yaml, regenerate). Skip when an existing skill already covers the request.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.