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 commands/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/commands/datopian/portaljs/portaljs-new-portal)<a href="https://agentmods.dev/commands/datopian/portaljs/portaljs-new-portal"><img src="https://agentmods.dev/badge/commands/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/commands/datopian/portaljs/portaljs-new-portal"><img src="https://agentmods.dev/badge/commands/datopian/portaljs/portaljs-new-portal.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.00028 | $0.03786 |
| Opus 5 | $0.00014 | $0.01893 |
| Sonnet 5 | $0.00006 | $0.00757 |
| Haiku 4.5 | $0.00003 | $0.00379 |
Grade C, and why
portaljs-new-portal scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "./$PROJECT_SLUG/node_modules" "./$PROJECT_SLUG/.next" How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/portaljs-new-portal
Scaffold a production-ready PortalJS data portal. 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, substitutes placeholder tokens, sets the namespace
mode, seeds any datasets, installs dependencies, and verifies the build.
The template you are scaffolding
examples/portaljs-catalog is the canonical template. It has three surfaces:
| Surface | Route | File | What it is |
|---|---|---|---|
| Home | / |
pages/index.tsx |
Search-first landing: hero + search box + suggested-query chips (__PROJECT_NAME__ / __DESCRIPTION__ tokens) |
| Catalog / search | /search |
pages/search.tsx |
Client-side full-text list over datasets.json |
| Dataset showcase | /@<namespace>/<slug> |
pages/[owner]/[slug].tsx |
One dataset: metadata, Table data preview, Download & API, and a Views placeholder for charts/maps |
The catalog is driven by datasets.json (the single source of truth) — each entry is
{ slug, name, description, file, format, namespace }. lib/datasets.ts exposes
getDatasets(), getDataset(slug), getDatasetByNamespace(ns, slug), datasetHref(d)
→ /@${namespace}/${slug}, and a NAMESPACE_TYPE: 'theme' | 'owner' constant.
A portal uses exactly one namespace mode:
'theme'— a single-publisher portal whose datasets are grouped by subject (e.g.@reference/country-codes). The showcase labels the namespace "Theme".'owner'— a multi-publisher portal whose datasets are grouped by who published them (e.g.@worldbank/country-codes). The showcase labels the namespace "Owner".
Search is a static client-side list for now. A live backend (e.g. CKAN, via
/portaljs-connect-ckan) can replace datasets.json later without changing the URL structure.
Required input — interview, don't error
You need a project name and one-line description. Datasets are optional at
scaffold time. Never dead-end with a missing-input error. If $ARGUMENTS is empty or
thin, run the structured interview in Step 1 to gather what's missing. The user can say
"use defaults" at any point to skip a round and accept the defaults below.
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 · 318 lines · 28 tokens per session scan C 5fab3426066b
portaljs-new-portal is a command published in the GitHub repository datopian/portaljs (2,350 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 3,786 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
laravel-ai-sdk
Build AI features with the first-party Laravel AI SDK (Laravel 13+); use the laravel:ai-sdk skill exactly as written.
speckit.archive.run
Archive merged feature specs into project memory with provenance, sweep discovery, and gated cleanup.
dare-llm-integration
Integração segura e eficiente com LLMs (Gemini, Claude, OpenAI, Ollama) em projetos DARE.
vlm-ocr-evaluation
Run the vlm-ocr skill in its evaluate phase: compare candidate OCR systems against a stratified human-transcribed ground-truth sample and pick a model on measured CER/WER before committing to a bulk run.
data-pipeline
You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing.