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/ai-agent-examples --skill github-configure-ci-workflowsgit 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/github-configure-ci-workflows)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/github-configure-ci-workflows"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/github-configure-ci-workflows/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/jfrog/ai-agent-examples/github-configure-ci-workflows"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/github-configure-ci-workflows.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.00067 | $0.01599 |
| Opus 5.5 | $0.00027 | $0.00640 |
| Sonnet 5.5 | $0.00013 | $0.00320 |
| Haiku 4.5 | $0.00007 | $0.00160 |
Grade C, and why
github-configure-ci-workflows scanned grade C 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.
Downloads and executes remote codehighSupply 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 Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `helm push` / `curl -T` | `jf rt upload "*.tgz" "{project-key}-helm-local/"` | How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Configure CI Workflows
Modifies GitHub Actions workflow files in remote GitHub repositories to integrate with JFrog Artifactory for dependency resolution and artifact publishing.
Inputs
github_repos-- list of owner/repo (e.g.,["myorg/my-app", "myorg/my-lib"])project_key-- JFrog project keyecosystems-- list from:npm,maven,pip,go,docker,helmoidc_provider_name-- OIDC provider name from the OIDC setup skill (empty string if OIDC is not available)github_host-- GitHub host URL (e.g.,https://github.comorhttps://github.mycompany.com)
Workflow Modifications
1. Discover existing workflows
After cloning the repo, check for workflow files:
ls .github/workflows/ 2>/dev/null
If no workflows exist, create a new one based on the detected ecosystems.
2. Add JFrog CLI setup step
Insert the jfrog/setup-jfrog-cli@v4 step early in each job, before any build steps.
If OIDC is available (oidc_provider_name is set):
permissions:
id-token: write
contents: read
- name: Setup JFrog CLI
uses: jfrog/setup-jfrog-cli@v4
env:
JF_URL: ${{ vars.JF_URL }}
with:
oidc-provider-name: {oidc_provider_name}
If OIDC is NOT available (secrets-based auth):
- name: Setup JFrog CLI
uses: jfrog/setup-jfrog-cli@v4
env:
JF_URL: ${{ vars.JF_URL }}
JF_ACCESS_TOKEN: ${{ secrets.JF_ACCESS_TOKEN }}
Also set the project key:
env:
JF_PROJECT: "{project-key}"
3. Replace build commands
| Original | JFrog CLI Equivalent |
|---|---|
npm install / npm ci |
jf npm install |
npm publish |
jf npm publish |
mvn install |
jf mvn install |
mvn deploy |
jf mvn deploy |
pip install -r requirements.txt |
jf pip install -r requirements.txt |
go build |
jf go build |
go publish |
jf go publish |
docker build |
docker build (unchanged) |
docker push |
jf docker push |
helm package |
helm package (unchanged) |
helm push / curl -T |
jf rt upload "*.tgz" "{project-key}-helm-local/" |
What ships with it
2 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 First seen · 174 lines · 67 tokens per session scan F caf69fc3ff2d
github-configure-ci-workflows is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,599 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C 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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…