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 jfrog-system-config-repogit 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-system-config-repo)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/jfrog-system-config-repo"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-system-config-repo/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/jfrog-system-config-repo"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-system-config-repo.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.00054 | $0.03392 |
| Opus 5 | $0.00027 | $0.01696 |
| Sonnet 5 | $0.00011 | $0.00678 |
| Haiku 4.5 | $0.00005 | $0.00339 |
Grade C, and why
jfrog-system-config-repo 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$TMPDIR" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Prefer **`jf api`** per [../../../platform-features/skills/jfrog-cli/jf-api-patterns.md](../../../platform-features/skills/jfrog-cli/jf-api-patterns.md) after `jf config`; **`curl`** remains valid **fallback**. How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog State Persistence
Prefer jf api per ../../../platform-features/skills/jfrog-cli/jf-api-patterns.md after jf config; curl remains valid fallback.
Manages manifest persistence for onboarding audit trails. Supports two backends:
- Artifactory (default) -- stores manifests in a dedicated JFrog generic repository
- Git -- commits and pushes manifests to a git repository
The backend is determined by state.destination in the manifest (defaults to artifactory).
Inputs (from manifest state section)
| Field | Default | Description |
|---|---|---|
state.destination |
artifactory |
artifactory or git |
state.artifactory.project |
system |
JFrog project key for manifest storage |
state.artifactory.repository |
system-configuration |
Generic repo key within the project |
state.git.repo |
(required if git) | Git repo in owner/repo format |
state.git.path |
/ |
Directory path in the git repo |
state.git.branch |
main |
Branch to commit to |
If the state section is missing from the manifest, default to Artifactory with system / system-configuration.
Constants
- Upload path pattern:
<ISO-8601-timestamp>/jfrog-configuration-manifest.yaml- Timestamp format:
YYYY-MM-DDTHH-MM-SSZ(e.g.,2026-02-17T15-30-00Z) - Same pattern for both Artifactory and git backends
- Timestamp format:
Security (Artifactory backend)
The Artifactory state project is restricted to platform admins only:
- All
admin_privilegesare set tofalse(no project-level admin can manage members or resources) - No users or groups are ever added to this project
- Only the platform admin token (used for onboarding operations) has read/write access
- Do not include the state project in the manifest's
jfrog_projectslist -- it is internal infrastructure managed by the onboarding agent
This applies to both the default system project and any custom project configured via state.artifactory.project.
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.
- 10d ago First seen · 348 lines · 54 tokens per session scan C 569894d6de89
jfrog-system-config-repo is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 3,392 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…