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 agentmods add skills/jfrog/claude-plugin/jfrog-setup-package-managersnpx skills add jfrog/claude-plugin --skill jfrog-setup-package-managersgit clone --depth 1 https://github.com/jfrog/claude-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/claude-plugin/jfrog-setup-package-managers)<a href="https://agentmods.dev/skills/jfrog/claude-plugin/jfrog-setup-package-managers"><img src="https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-setup-package-managers.svg" alt="Measured on agentmods" 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 | $0.00175 | $0.03619 |
| Opus 5 | $0.00088 | $0.01809 |
| Sonnet 5 | $0.00035 | $0.00724 |
| Haiku 4.5 | $0.00017 | $0.00362 |
Grade A, and why
jfrog-setup-package-managers 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 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.
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.
This is a copy
100% identical to jfrog-setup-package-managers — 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.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog — Setup Package Managers for Artifactory
In examples below, <skill_path> is this skill's directory (parent of
scripts/ / references/).
Apply the session hook's repo pick via jf setup,
then record it in .jfrog/local/package-resolution.json
via scripts/merge-workspace-binding.sh.
jf setup writes package-manager-native config (.npmrc, pip.conf, uv.toml, …); the binding
lets the hook re-apply on later sessions.
At a glance (always-read core)
Every jf setup this session:
- Cover base
../jfrog/SKILL.mdAt-a-glance / Tier A (Step 0.1) →<UA>,--server-idplacement, single-server, stop-don't-switch. Prefer full base SKILL.md when you can; Tier B (cli-gotchas/jf-api/ …) only if the next action needsjf api/ advanced CLI - Always
--repo+--server-id.<repoKey>← Step 2 (table / binding / global-cache) or user override / unresolved AskQuestion; never self-discover.<SID>← resolver only (never user-selected) - Confirm before first
jf setupunless user asked silent / non-interactive - Exit 0 → merge binding; non-zero → stop, surface CLI verbatim, offer
alternate repo or
abort(2-answer cap) - Binding = decisions, not creds — never write tokens into
.jfrog/local/package-resolution.json - Unresolved / failed: ask with failure verbatim — never switch servers
- Never skip Gotchas + base Tier A hard
rules (
../jfrog/SKILL.mdCautious execution / Server selection / Tier A gotcha floor). Fullcli-gotchas.mdis Tier B — not required forjf setup
What ships with it
4 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.
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.
- 4d ago First seen · 264 lines · 175 tokens per session scan A 380524bddefe
jfrog-setup-package-managers is a skill published in the GitHub repository jfrog/claude-plugin (6 stars, last pushed today), licensed Apache-2.0. It adds 175 tokens to every session and 3,619 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to jfrog-setup-package-managers, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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…