jfrog-package-curation

jfrog-package-curation is a skill for Claude Code, Codex from jfrog/claude-plugin. It costs 189 tokens per session (3,670 once invoked), scanned A, a copy of jfrog-package-curation, Apache-2.0.

A tool for checking and downloading packages from JFrog, a software package and artifact management platform. It covers packages such as npm, Maven, PyPI, Go, and NuGet, including whether a version is available and allowed by curation rules.

In plain words
What is it for?
Use it before downloading a dependency or when investigating package-install failures such as ETARGET, 403, or missing-distribution errors.
Why use it?
It helps explain why a package cannot be installed, such as a missing version, a blocked security policy, or an approved exception that is not being applied.

Skill for Claude CodeCodex

Part of the jfrog plugin — 7 skills, 4 hooks, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/jfrog/claude-plugin/jfrog-package-curation
Any agent
npx skills add jfrog/claude-plugin --skill jfrog-package-curation
Clone the repo
git clone --depth 1 https://github.com/jfrog/claude-plugin

Made for: Claude Code, Codex.

Or install jfrog, the plugin that ships this one along with the rest of its 7 skills, 4 hooks, 1 MCP server.

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 jfrog-package-curation

README.md
[![agentmods](https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-package-curation.svg)](https://agentmods.dev/skills/jfrog/claude-plugin/jfrog-package-curation)
Your own site
<a href="https://agentmods.dev/skills/jfrog/claude-plugin/jfrog-package-curation"><img src="https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-package-curation.svg" alt="Measured on agentmods" height="20"></a>
Per session 189 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,670 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00189 $0.03670
Opus 5 $0.00095 $0.01835
Sonnet 5 $0.00038 $0.00734
Haiku 4.5 $0.00019 $0.00367

Measured 4d ago against content hash 93bed5b3b2e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

jfrog-package-curation 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 4d 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.

**Interpreting the result with `jf api`**: unlike plain `curl`, `jf api`
Origin

This is a copy

100% identical to jfrog-package-curation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/jfrog-package-curation/SKILL.md · 315 lines

How it starts

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

JFrog Package Curation

Prerequisites

  • Read ../jfrog/SKILL.md for JFrog Platform concepts, domain model, CLI setup, and API patterns.
  • OneModel shapes drift by server version. Before inventing GraphQL fields or where filters, read ../jfrog/references/onemodel-graphql.md (schema fetch workflow) and ../jfrog/references/onemodel-query-examples.md (Public packages, Stored packages). Regenerate or verify queries against GET "$JFROG_URL/onemodel/api/v1/supergraph/schema" when examples fail validation.

Which path do I need?

  • Package hasn't been checked or downloaded yet (is it safe / allowed / curated? download it) → go to Check & download below.
  • A package operation already failedETARGET (npm), "no matching distribution" (pip), NU1102 (NuGet), a version missing/stripped from the registry, 403 / "blocked by curation policy", or an approved waiver not taking effect → go to Troubleshoot a failure below.

Troubleshoot a failure

Requires the JFrog MCP curation tools (jfs_curation_*); no jf CLI equivalent is used in this path. See the skill's compatibility note.

Root-causing a curation-attributable failure (ETARGET, 403, a version missing from the index, a waiver not taking effect) is a multi-step investigation — preflight checks, the two-gate model, symptom classification, then a full RCA procedure. It doesn't belong inline here since a plain download never touches it. Open references/rca-procedure.md and follow it from the top — one file, covering preflight, the #1 RULE, the two-gate model, symptom classification (Step 0), and the RCA itself (Steps 1–4, worked examples, gotchas).


Check & download

Workflow overview

flowchart TD
    A[User requests package check / download] --> B{Package in Public Catalog?}
    B -->|Yes| C[Get latest version from Catalog]
    B -->|No| D{Package in JFrog Platform Stored Packages?}
    D -->|Yes| E[Get latest version from Stored Packages]
    D -->|No| F[Package not found — stop]
    C --> G{Latest version in JFrog Platform?}
    E --> G
    G -->|Yes| H[Safe — download from JFrog Platform]
    G -->|No| I{Curation entitled?}
    I -->|Yes| J[Check curation policy via API]
    I -->|No| K[Download via remote repo]
    J -->|200 Allowed| K
    J -->|403 Blocked| M[Report curation blocked — see Troubleshoot a failure]

Read the full file on GitHub · 315 lines

Files

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.

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. 4d ago First seen · 315 lines · 189 tokens per session scan A 93bed5b3b2e8

Subscribe to this mod's changes

jfrog-package-curation is a skill published in the GitHub repository jfrog/claude-plugin (6 stars, last pushed today), licensed Apache-2.0. It adds 189 tokens to every session and 3,670 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to jfrog-package-curation, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens