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-add-datasetWrote 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-add-dataset)<a href="https://agentmods.dev/commands/datopian/portaljs/portaljs-add-dataset"><img src="https://agentmods.dev/badge/commands/datopian/portaljs/portaljs-add-dataset/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-add-dataset"><img src="https://agentmods.dev/badge/commands/datopian/portaljs/portaljs-add-dataset.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.00066 | $0.04673 |
| Opus 5 | $0.00033 | $0.02337 |
| Sonnet 5 | $0.00013 | $0.00935 |
| Haiku 4.5 | $0.00007 | $0.00467 |
Grade A, and why
portaljs-add-dataset scanned grade A 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fL "$SOURCE" -o "/tmp/$DATASET_SLUG.$EXT" How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/portaljs-add-dataset
Add a dataset to an existing PortalJS (portaljs-catalog) portal. Appends one entry to
datasets.json — the single source of truth for the catalog — and routes the data to
the right place by source first, then size. No per-dataset page is created: the catalog
at /search lists it and the dynamic showcase route pages/[owner]/[slug].tsx renders it
automatically at /@<namespace>/<slug>.
The routing matrix — branch on SOURCE, then size
Where the bytes end up depends first on where they come from, then on size/intent. The
manifest's resource.path (or single-file file) is the unifying abstraction:
resourceUrl() in lib/datasets.ts serves a repo-relative path from /public/data and
passes an absolute URL straight through. So every route below just decides what string
to write into path.
| Source | Default | What happens | Manifest path |
|---|---|---|---|
| Local file | R2 via Git LFS | mv into the repo, git lfs track <path>, commit a ~134 B pointer, git lfs push → Giftless → R2 (no GitHub remote needed) |
absolute R2 URL (browser fetches R2 directly) |
| Local file (fenced) | inline | Only bundled SAMPLE data or an OSS self-host with no R2: cp into public/data/ (stays inline per .gitattributes fence) |
bare filename → /data/<file> |
| Remote URL | passthrough | record the URL as-is — no download, no upload, zero duplication | the absolute URL, unchanged |
| Remote URL | adopt (opt-in) | user wants it hosted/versioned under the portal: fetch → route as a local file (R2/LFS) | absolute R2 URL |
Storage decision (epic po-g9y): the default for added data is R2, regardless of size or format. Inline is not a size threshold — it is a fenced exception for bundled sample data and the OSS-no-R2 fallback. Remote URLs default to passthrough (copy nothing); adopting one into R2 is an explicit opt-in.
Remote-URL passthrough caveat: serving and linking always work. But in-browser range / DuckDB queries against a 3rd-party URL need CORS + range support on that host, which we don't control. If the user needs querying (not just preview/download) and the remote lacks CORS/range, recommend the adopt-into-R2 option.
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.
- 10d ago First seen · 326 lines · 66 tokens per session scan A 7baf2323272a
portaljs-add-dataset is a command published in the GitHub repository datopian/portaljs (2,350 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 4,673 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.