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-create-reposnpx skills add jfrog/ai-agent-examples --skill jfrog-create-reposgit 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-create-repos)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/jfrog-create-repos"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-create-repos.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.1 | $0.00083 | $0.04444 |
| Opus 5 | $0.00042 | $0.02222 |
| Sonnet 5 | $0.00017 | $0.00889 |
| Haiku 4.5 | $0.00008 | $0.00444 |
Grade A, and why
jfrog-create-repos 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 6d 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.
Prefer **`jf api`** ([../../../platform-features/skills/jfrog-cli/jf-api-patterns.md](../../../platform-features/skills/jfrog-cli/jf-api-patterns.md)) after `jf config`; **`curl`** snippets are **fallback** when the CLI How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog Create Repositories
Prefer jf api (../../../platform-features/skills/jfrog-cli/jf-api-patterns.md) after jf config; curl snippets are fallback when the CLI is unavailable.
Creates repositories scoped to a JFrog project. Supports three modes:
- Ecosystem-only -- auto-generates standard trios (local + remote + virtual) per ecosystem
- Repositories-only -- creates exactly the repos listed in custom definitions
- Both (smart merge) -- generates ecosystem trios, then applies custom overrides and additions
Inputs
project_key-- the JFrog project key (must already exist)ecosystems-- (optional) list from:npm,maven,pip,go,docker,helmrepositories-- (optional) list of custom repository definitions from the manifest (see schema intemplates/manifest-template.yaml)xray_enabled-- boolean, resolved by the orchestration skill (per-project override or global default). Whentrue, Xray indexing is enabled on local and remote repos and{{XRAY_INDEX}}in templates is set totrue. Whenfalse, indexing is skipped and{{XRAY_INDEX}}is set tofalse.curation_enabled-- boolean, resolved by the orchestration skill (per-project override or global default). Whentrue, Curation is activated on remote repos after creation.naming_pattern-- (optional) object fromdetect-existing-patternsskill that controls how repo names are generated. When not provided, the standard pattern is used. See Dynamic Naming below.
At least one of ecosystems or repositories must be provided. If neither is set, skip repo creation for this project.
Repository Naming
Standard Pattern (default)
The standard naming convention, used when naming_pattern is not provided:
| Ecosystem | Local | Remote | Virtual |
|---|---|---|---|
| npm | {key}-npm-local |
{key}-npm-remote |
{key}-npm |
| maven | {key}-maven-local |
{key}-maven-remote |
{key}-maven |
| pip | {key}-pypi-local |
{key}-pypi-remote |
{key}-pypi |
| go | {key}-go-local |
{key}-go-remote |
{key}-go |
| docker | {key}-docker-local |
{key}-docker-remote |
{key}-docker |
| helm | {key}-helm-local |
{key}-helm-remote |
{key}-helm |
What ships with it
3 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.
- 6d ago First seen · 385 lines · 83 tokens per session scan A b98431a9d929
jfrog-create-repos is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 4,444 once invoked, about $0.0004 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.