What is jpl-explorer-1?

A design system for public-facing NASA Jet Propulsion Laboratory websites, offering Vue components and compiled assets that can work without a specific framework. Vue is a JavaScript tool for building web interfaces.

Use it for approved JPL public-facing products to reuse Explorer 1 components or compiled assets, preserve the project’s build setup, add documented customisations, and test keyboard use, focus, errors, contrast, zoom, and responsive layouts.

It gives authorised JPL public sites shared visual and interaction patterns while keeping them separate from mission-operations tools and unrelated NASA projects. It also helps teams use the official delivery path and check accessibility.

jpl-explorer-1 — Skill for Claude Code and Codex by blencorp

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 blencorp/skills --skill jpl-explorer-1

Clone the repo

git clone --depth 1 https://github.com/blencorp/skills

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/blencorp/skills/jpl-explorer-1/github.svg)](https://agentmods.dev/skills/blencorp/skills/jpl-explorer-1)

Your own site

<a href="https://agentmods.dev/skills/blencorp/skills/jpl-explorer-1"><img src="https://agentmods.dev/badge/skills/blencorp/skills/jpl-explorer-1/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/blencorp/skills/jpl-explorer-1"><img src="https://agentmods.dev/badge/skills/blencorp/skills/jpl-explorer-1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 459 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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.00459
Opus 5	$0.00025	$0.00230
Sonnet 5	$0.00010	$0.00092
Haiku 4.5	$0.00005	$0.00046

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

Security

Grade A, and why

jpl-explorer-1 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 9d 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.

federal/jpl-explorer-1/SKILL.md · 39 lines

How it starts

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

NASA JPL Explorer 1

Build within the system's documented scope and delivery model.

Before editing

Confirm the product owner and that this system is authorized for the target surface.
Read references/implementation.md before installing or changing dependencies.
Read references/sources.md when checking versions, provenance, license, or release state.
Inspect the existing framework, package manager, asset pipeline, and accessibility tests. Preserve them unless the official integration requires a change.

Workflow

Choose one documented delivery path; do not mix compiled, source, CDN, and framework-wrapper paths accidentally.
Pin the dependency or downloaded asset version and keep upstream notices.
Reuse official components, tokens, content guidance, and templates before adding custom UI.
Extend through documented tokens, properties, slots, Sass settings, or composition. Do not edit vendored package files.
Test semantic structure, keyboard operation, focus order and visibility, accessible names, error recovery, zoom/reflow, contrast, and target browsers.
Report custom patterns, unsupported requirements, and upstream gaps explicitly.

Boundaries

Scope: JPL public-facing products governed by Explorer 1. Route spacecraft-operations tools to Stellar and NASA-wide modernization work to Horizon when appropriate.
Release: active official repository and published packages.
Delivery: Vue component library plus compiled shared assets for HTML or other frameworks.
Do not invent component APIs, tokens, package names, or compliance claims.
Do not import another jurisdiction's branding to fill a gap.
A passing component example does not prove the completed service conforms to WCAG, Section 508, the ADA, or local policy.

References

Implementation — packages, setup, and integration decisions
Sources — authoritative URLs, snapshot versions, ownership, and license notes

Read the full file on GitHub · 39 lines

Files

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.

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.

9d ago First seen · 39 lines · 50 tokens per session scan A a0c85be94d6e

Subscribe to this mod's changes

jpl-explorer-1 is a skill published in the GitHub repository blencorp/skills (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 50 tokens to every session and 459 once invoked, about $0.0003 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.

Frontend Vue and Svelte

shadcn-svelte

Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.

vercel-labs/json-render · 63 tokens

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

jpl-explorer-1