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.
npx skills add jfrog/cursor-plugin --skill jfrog-initgit clone --depth 1 https://github.com/jfrog/cursor-pluginWrote 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/skills/jfrog/cursor-plugin/jfrog-init)<a href="https://agentmods.dev/skills/jfrog/cursor-plugin/jfrog-init"><img src="https://agentmods.dev/badge/skills/jfrog/cursor-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.
<a href="https://agentmods.dev/skills/jfrog/cursor-plugin/jfrog-init"><img src="https://agentmods.dev/badge/skills/jfrog/cursor-plugin/jfrog-init.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.00031 | $0.06991 |
| Opus 5.5 | $0.00012 | $0.02796 |
| Sonnet 5.5 | $0.00006 | $0.01398 |
| Haiku 4.5 | $0.00003 | $0.00699 |
Grade C, and why
jfrog-init 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 29d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
`~/.netrc` write (same, see `references/marketplace-setup.md`); and This is a copy
100% identical to jfrog-init — 18 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.
How it starts
The opening of the file, as written. The whole thing — 504 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—AskUserQuestionYes/No before auto-installing (Step 1).jf(JFrog CLI) —AskUserQuestionYes/No before auto-installing (Step 2).jf config—AskUserQuestionpicker (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
AskUserQuestionpicker 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.jfrogwrite (both unattended, noAskUserQuestion— seereferences/script-invocation.md); Step 8's~/.netrcwrite (same, seereferences/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.
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.
- references/batch-walk.md 3.1 KB
- references/catalog-runtime-branches.md 3.7 KB
- references/final-summary-rendering.md 5.4 KB
- references/flow-diagram.md 7.2 KB
- references/how-to-ask-user.md 1.4 KB
- references/invoking-and-output-rules.md 3.7 KB
- references/jf-cli-install-internals.md 4.4 KB
- references/jf-cli-install-prompt.md 2.9 KB
- references/jf-cli-update-prompt.md 2.2 KB
- references/jf-config-auth-picker.md 9.5 KB
- references/marketplace-setup.md 1.3 KB
- references/mcp-plugin-config.md 19 KB
- references/node-install-prompt.md 3.2 KB
- references/out-of-scope.md 1.5 KB
- references/project-matching.md 2.2 KB
- references/project-picker.md 5.9 KB
- references/project-resolution-branches.md 2.6 KB
- references/project-state-reuse.md 2.3 KB
- references/script-invocation.md 13 KB
- references/server-picker.md 2.6 KB
- scripts/jfrog-add-claude-marketplace.mjs 3.5 KB runs code
- scripts/jfrog-detect-all.mjs 13 KB runs code
- scripts/jfrog-detect-catalog-runtime.mjs 11 KB runs code
- scripts/jfrog-detect-jf-cli.mjs 5.4 KB runs code
- scripts/jfrog-detect-jf-config.mjs 1.5 KB runs code
- scripts/jfrog-detect-jfrog-mcp-responding.mjs 3.1 KB runs code
- scripts/jfrog-detect-jfrog-mcp.mjs 7.7 KB runs code
- scripts/jfrog-detect-opencode-mcp-auth.mjs 2.8 KB runs code
- scripts/jfrog-detect-project.mjs 6.3 KB runs code
- scripts/jfrog-detect-server-ping.mjs 7.6 KB runs code
- scripts/jfrog-install-jf-cli.mjs 24 KB runs code
- scripts/jfrog-login-register-session.mjs 4.7 KB runs code
- scripts/jfrog-login-save-credentials.mjs 6.8 KB runs code
- scripts/jfrog-reinstall-jfrog-plugin.mjs 6.8 KB runs code
- scripts/jfrog-resolve-jf-server.mjs 4.2 KB runs code
- scripts/jfrog-resolve-mcp-config.mjs 26 KB runs code
- scripts/jfrog-state-file.mjs 11 KB runs code
- scripts/jfrog-substitute-mcp-placeholders.mjs 4.9 KB runs code
- scripts/jfrog-write-opencode-mcp.mjs 5.2 KB runs code
- scripts/lib/claude-config.mjs 2.4 KB runs code
- scripts/lib/claude.mjs 543 B runs code
- scripts/lib/command.mjs 4.7 KB runs code
- scripts/lib/jf-api.mjs 2.4 KB runs code
- scripts/lib/jf.mjs 21 KB runs code
- scripts/lib/netrc.mjs 2.2 KB runs code
- scripts/lib/project-cache.mjs 4.4 KB runs code
- scripts/lib/projects.mjs 7.2 KB runs code
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.
- 29d ago Changed · +5 lines 79e6f16457ff
- 1mo ago Changed · -104 lines 0e11a9d79881
- 1mo ago First seen · 603 lines · 31 tokens per session scan C 2dbca5ea7b04
jfrog-init is a skill published in the GitHub repository jfrog/cursor-plugin (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 31 tokens to every session and 6,991 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (reaches for credential files). It is 100% identical to jfrog-init, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…