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/ai-agent-examples/jfrog-clinpx skills add jfrog/ai-agent-examples --skill jfrog-cligit clone --depth 1 https://github.com/jfrog/ai-agent-examplesWhat 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.00088 | $0.01635 |
| Opus 5 | $0.00044 | $0.00817 |
| Sonnet 5 | $0.00018 | $0.00327 |
| Haiku 4.5 | $0.00009 | $0.00163 |
Grade B, and why
JFrog CLI scanned grade B with 2 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 2d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fL https://install-cli.jfrog.io | sh Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Linux (curl) — runs remote script; for production prefer package manager or verify script integrity How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog CLI Skill
Installation
See Install JFrog CLI.
# macOS
brew install jfrog-cli
# Linux (curl) — runs remote script; for production prefer package manager or verify script integrity
curl -fL https://install-cli.jfrog.io | sh
# Docker
docker run releases-docker.jfrog.io/jfrog/jfrog-cli jf --version
Requires JFrog CLI 2.100.0+ for jf api (platform REST). Other jf commands need a recent v2.x CLI.
Authentication
Follow login-flow.md to resolve the active JFrog environment. The jf CLI is required and will be installed automatically if missing. The flow supports multiple environments and persists credentials via jf config (encrypted at rest):
- Ensure
jfis installed at 2.100.0+ (required forjf api). - Check saved credentials -- runs
jf config showto list configured servers. If multiple are saved, asks the user which environment to use. - Confirm platform URL -- show URLs from
jf config show; user confirms or switches server. - Readiness --
jf api /artifactory/api/v1/system/readinessafter confirmation. - Agent-driven web login -- if no credentials exist, asks the user for their JFrog URL, drives the REST-based login flow (user clicks a link, authenticates in browser), and saves the resulting token via
jf config add.
After login, credentials are saved with a server ID derived from the hostname (e.g. mycompany from mycompany.jfrog.io) so the user can switch between environments with jf config use <server-id>.
Platform REST via jf api
Prefer jf api <path> for JFrog Platform HTTP APIs (path only; auth from jf config). See jf-api-patterns.md for session start (confirm URL → readiness), status/body capture, and curl fallback rules.
Configuration
# List configurations
jf config show
# Set default server (if multiple configured)
jf config use my-server
# Add server configuration (non-interactive, using env vars)
jf config add my-server \
--url=https://$JFROG_URL \
--access-token=$JFROG_ACCESS_TOKEN \
--interactive=false
# Export/import config (for CI). Never commit the export file; add it to .gitignore.
jf config export my-server > jf-config.export
jf config import jf-config.export
What ships with it
6 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.
- 2d ago First seen · 152 lines · 88 tokens per session scan B 7bb95d0aff72
JFrog CLI is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,635 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.