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/jfrog-skills --skill jfrog-setup-package-managersgit clone --depth 1 https://github.com/jfrog/jfrog-skillsWrote 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/jfrog-skills/jfrog-setup-package-managers)<a href="https://agentmods.dev/skills/jfrog/jfrog-skills/jfrog-setup-package-managers"><img src="https://agentmods.dev/badge/skills/jfrog/jfrog-skills/jfrog-setup-package-managers.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 26 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 76 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 76 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 43 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium MCP Rug Pull · line 96 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
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.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 8d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- jfrog-setup-package-managers — 100% identical, 0 lines differ
- jfrog-setup-package-managers — 100% identical, 0 lines differ
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.
- 8d 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/jfrog-skills (22 stars, last pushed yesterday), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
arkcli-doctor
A diagnostic tool for ARK services, accounts, models, and inference endpoints. An inference endpoint is the online address through which an AI model receives requests.
arkcli-models
A catalogue and lookup tool for ARK AI models, including their versions, supported input types, context limits, and lifecycle status. It can also list models belonging to your account.
arkcli-gen
An ArkCLI workflow for generating images and videos with Ark models. Image results return immediately, while video generation runs as a background job that must be checked until finished.
arkcli-custommodel
A manager for custom AI models: model files that you trained or fine-tuned yourself. It can import them, show their status and details, change descriptions, remove them, or prepare them for deployment.
arkcli-plans
A subscription manager for ARK Agent Plans and Coding Plans, including personal and team subscriptions. It also manages team seats, which are assigned places for employees, and their API keys.
arkcli-profile
A local profile manager for ArkCLI. A profile groups an identity type, region, project, owner, and API keys, with different profile types for platform and plan-based access.