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/github-configure-ci-workflowsnpx skills add jfrog/ai-agent-examples --skill github-configure-ci-workflowsgit 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.00067 | $0.01599 |
| Opus 5 | $0.00034 | $0.00800 |
| Sonnet 5 | $0.00013 | $0.00320 |
| Haiku 4.5 | $0.00007 | $0.00160 |
Grade F, and why
github-configure-ci-workflows scanned grade F with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo mv jf /usr/local/bin/jf 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 Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
cd / && rm -rf "$TMPDIR" 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.
- 2d 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 2mo 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. A static security scan graded it F with 4 findings (asks for root, downloads and executes remote code, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.
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/.