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-distributionnpx skills add jfrog/ai-agent-examples --skill jfrog-distributiongit clone --depth 1 https://github.com/jfrog/ai-agent-examplesWrote 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/ai-agent-examples/jfrog-distribution)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/jfrog-distribution"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-distribution.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.00057 | $0.01789 |
| Opus 5 | $0.00028 | $0.00894 |
| Sonnet 5 | $0.00011 | $0.00358 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
JFrog Distribution scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> **API transport:** Prefer **`jf api`** (JFrog CLI 2.100.0+). See [jf-api-patterns.md](../jfrog-cli/jf-api-patterns.md) (path-only URLs; auth from `jf config`). Examples using **`curl`** with `$JFROG_URL` + bearer token How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API transport: Prefer
jf api(JFrog CLI 2.100.0+). See jf-api-patterns.md (path-only URLs; auth fromjf config). Examples usingcurlwith$JFROG_URL+ bearer token are fallback when the CLI is missing or below 2.100.0.
JFrog Distribution Skill
Authentication
All requests require an access token via the Authorization header:
Authorization: Bearer $JFROG_ACCESS_TOKEN
Base URLs:
- Release Lifecycle:
https://$JFROG_URL/lifecycle/api/... - Distribution:
https://$JFROG_URL/distribution/api/... - Evidence:
https://$JFROG_URL/evidence/api/...
When authentication is needed, follow the login-flow.md procedure to resolve the active JFrog environment. The jf CLI is required and will be installed automatically if missing. The agent checks saved credentials via jf config show and asks which environment to use if multiple are saved. If none exist, the agent drives the web login flow and saves credentials via jf config add.
Pre-flight: Before operations, verify the Lifecycle service is available:
GET $JFROG_URL/lifecycle/api/v2/promotion/records?limit=1(expect HTTP 200). If unavailable, inform the user that Release Lifecycle Management is not deployed on this instance and stop.
Core Concepts
| Concept | Description |
|---|---|
| Release Bundle v2 | Immutable, GPG-signed, versioned collection of artifacts representing a release candidate |
| Environment | SDLC stage (DEV, STAGING, PROD) for organizing the promotion pipeline |
| Promotion | Moving a Release Bundle from one environment to the next (with optional security gate checks) |
| Distribution | Delivering Release Bundle content to remote Edge nodes |
| Edge Node | Remote Artifactory instance that receives distributed content |
| Evidence | Signed attestation (DSSE format) attached to artifacts, builds, or release bundles for auditing |
Release Lifecycle Workflow
What ships with it
1 file 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 · 183 lines · 57 tokens per session scan A 01c5572d6157
JFrog Distribution is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,789 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (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
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.