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 skills-il/developer-tools --skill jfrog-devopsgit clone --depth 1 https://github.com/skills-il/developer-toolsWrote 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/skills-il/developer-tools/jfrog-devops)<a href="https://agentmods.dev/skills/skills-il/developer-tools/jfrog-devops"><img src="https://agentmods.dev/badge/skills/skills-il/developer-tools/jfrog-devops/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/skills-il/developer-tools/jfrog-devops"><img src="https://agentmods.dev/badge/skills/skills-il/developer-tools/jfrog-devops.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.00168 | $0.06597 |
| Opus 5.5 | $0.00067 | $0.02639 |
| Sonnet 5.5 | $0.00034 | $0.01319 |
| Haiku 4.5 | $0.00017 | $0.00660 |
Grade B, and why
jfrog-devops 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 1mo 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.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
# Collect environment variables 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.
allowed-tools: Bash(curl:*) Bash(jf:*) Bash(docker:*) Bash(python3:*) How it starts
The opening of the file, as written. The whole thing — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog DevOps
Instructions
Step 1: Identify the DevOps Operation
| Operation | JFrog Tool | API/CLI | Auth Required |
|---|---|---|---|
| Upload/deploy artifact | Artifactory | PUT /{repo}/{path} or jf rt upload | Yes |
| Download artifact | Artifactory | GET /{repo}/{path} or jf rt download | Yes (unless anonymous) |
| Search artifacts | Artifactory | AQL or jf rt search | Yes |
| Docker push/pull | Artifactory | Docker API or jf docker | Yes |
| Publish build info | Artifactory | PUT /api/build or jf rt build-publish | Yes |
| Promote build | Artifactory | POST /api/build/promote | Yes (admin) |
| Scan for CVEs | Xray | POST /api/v1/scanArtifact or jf xr scan | Yes |
| Create watch/policy | Xray | POST /api/v2/watches | Yes (admin) |
| Generate report | Xray | POST /api/v1/reports/vulnerabilities | Yes |
| Export SBOM (SPDX or CycloneDX) | Xray | POST /xray/api/v2/component/exportDetails, or jf scan --format=cyclonedx (CycloneDX only) | Yes |
| Vet OSS packages before download | Curation | Configured per remote repo | Yes (admin) |
| Manage ML model (Hugging Face, MLflow, NIM) | Artifactory ML repo | jf rt upload or FrogML SDK | Yes |
| Cleanup old artifacts | Artifactory | AQL + delete or retention policies | Yes (admin) |
Step 2: Configure Authentication
Option A: JFrog CLI (recommended):
# Configure JFrog CLI with access token (recommended)
jf config add my-server \
--url="https://acme.jfrog.io" \
--access-token="YOUR_ACCESS_TOKEN" \
--interactive=false
# Verify connection
jf rt ping
Option B: REST API with curl:
# Read the host and token from the environment so neither is hardcoded
# or left in shell history. JF_URL is your platform base URL.
export JF_URL="https://acme.jfrog.io"
# Using access token (recommended)
curl -H "Authorization: Bearer $JF_ACCESS_TOKEN" \
"$JF_URL/artifactory/api/system/ping"
# Using identity token (reference token, also works as Bearer)
curl -H "Authorization: Bearer $JF_REFERENCE_TOKEN" \
"$JF_URL/artifactory/api/system/ping"
What ships with it
8 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.
- 1mo ago Changed d797e6bd2864
- 1mo ago Changed · +30 lines a8fdb5955e46
- 1mo ago First seen · 362 lines · 168 tokens per session scan B 0aaadd5c2b02
jfrog-devops is a skill published in the GitHub repository skills-il/developer-tools (13 stars, last pushed 3d ago), licensed MIT. It adds 168 tokens to every session and 6,597 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it B with 2 findings (harvests environment variables, 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
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…