A setup and troubleshooting command for the JFrog plugin, a tool used to work with JFrog package and artifact services. It checks required software and configuration in a fixed order, stopping at the first failed check and guiding the matching fix.

First-time installation, completing JFrog configuration, verifying login or access-token setup, selecting a project, and diagnosing a broken plugin setup.

It helps identify whether Node, the JFrog command-line tool, login, or project selection is preventing the plugin from working.

jfrog-init — Skill for Claude Code by jfrog/claude-plugin

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 jfrog/claude-plugin --skill jfrog-init

Clone the repo

git clone --depth 1 https://github.com/jfrog/claude-plugin

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-init/github.svg)](https://agentmods.dev/skills/jfrog/claude-plugin/jfrog-init)

Your own site

<a href="https://agentmods.dev/skills/jfrog/claude-plugin/jfrog-init"><img src="https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-init/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/jfrog/claude-plugin/jfrog-init"><img src="https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 7,062 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 89% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.07062
Opus 5.5	$0.00012	$0.02825
Sonnet 5.5	$0.00006	$0.01412
Haiku 4.5	$0.00003	$0.00706

Measured 3d ago against content hash ab3d907bf5ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jfrog-init 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 3d ago.

The scan reads SKILL.md. This mod also ships 27 executable files (scripts/jfrog-add-claude-marketplace.mjs, scripts/jfrog-detect-all.mjs, scripts/jfrog-detect-catalog-runtime.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

89% identical to jfrog-init — 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-init/SKILL.md · 506 lines

How it starts

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

/jfrog-init — verify and guide JFrog plugin readiness

First output must be a tool call, not text. No "I'll start..." preamble.

Walks a fixed, ordered checklist and stops at the first non-passing result, guiding the user through the matching fix before re-checking. Every detector in scripts/ is idempotent, read-only, JSON-emitting, and implemented in Node (.mjs), so the same detector runs unmodified on macOS, Linux, and Windows. Step 3's web-login uses this skill's own local .mjs scripts, same as every other step. The one interactive fix step that isn't a Node script at all is Step 1's Node install itself — a missing Node can't run a .mjs installer, so that one step branches on OS or shell directly.

Approval model — every user-approval point is detailed in its own Step below (exact wording, AskUserQuestion payloads, forbidden phrases); this is just the map:

node — AskUserQuestion Yes/No before auto-installing (Step 1).
jf (JFrog CLI) — AskUserQuestion Yes/No before auto-installing (Step 2).
jf config — AskUserQuestion picker (web login, in-session, vs. access token, which never enters this conversation) (Step 3/4).
Project selection — the user answers with a project name or key; an AskUserQuestion picker offers the first two enumerated projects plus "Other" (Step 6).
Everything else is read-only, except: Step 5's placeholder substitution and OpenCode-only mcp.jfrog write (both unattended, no AskUserQuestion — see references/script-invocation.md); Step 8's headers-helper install and Claude Code config writes (same, see references/marketplace-setup.md); and the Final summary's state write below.

Step 1's nvm install and jfrog-install-jf-cli.mjs, Step 3's web-login scripts, Step 8's jfrog-add-claude-marketplace.mjs call, and the Final summary's jfrog-state-file.mjs set call are deliberately not in allowed-tools and will raise the harness's own approval prompt — intended, not a misconfiguration; see references/script-invocation.md.

Read the full file on GitHub · 506 lines

Files

What ships with it

47 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.

3d ago Changed · +2 lines scan C → A ab3d907bf5ea
29d ago Changed · +5 lines 79e6f16457ff
1mo ago Changed · -104 lines 0e11a9d79881
1mo ago Changed · -1 lines 2dbca5ea7b04
1mo ago First seen · 604 lines · 31 tokens per session scan C 56a471cccc7f

Subscribe to this mod's changes

jfrog-init is a skill published in the GitHub repository jfrog/claude-plugin (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 7,062 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to jfrog-init, differing in 0 lines, and is treated as a copy.

Debugging

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens