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/claude-plugin/jfrog-ai-catalognpx skills add jfrog/claude-plugin --skill jfrog-ai-cataloggit clone --depth 1 https://github.com/jfrog/claude-pluginWrote 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/claude-plugin/jfrog-ai-catalog)<a href="https://agentmods.dev/skills/jfrog/claude-plugin/jfrog-ai-catalog"><img src="https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-ai-catalog.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.00110 | $0.01870 |
| Opus 5 | $0.00055 | $0.00935 |
| Sonnet 5 | $0.00022 | $0.00374 |
| Haiku 4.5 | $0.00011 | $0.00187 |
Grade C, and why
jfrog-ai-catalog scanned grade C 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 7d 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.
D -->|List installed skills / remove| G[jf skills list / rm -rf install dir] This is a copy
100% identical to jfrog-ai-catalog — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog AI Catalog
Discover, install, and manage agent skills and agent plugins from the JFrog AI
Catalog (Artifactory skills/plugins repositories), and publish your own back to
it, all through the JFrog CLI (jf skills, jf agent plugins) and the JFrog
Agent Guard.
Choose a reference file
Pick the row matching the user's intent and read that reference file.
| Intent | Read |
|---|---|
| "What skills are available?" / browse the catalog / list versions / search by name | references/discovering-skills.md |
| Install or update a skill (latest or a pinned version), or a download is blocked | references/installing-skills.md |
| "What's installed?" / remove an installed skill | references/managing-installed-skills.md |
| Publish / upload / release a skill to the catalog | references/publishing-skills.md |
| "What plugins are available?" / browse the plugin catalog / list plugin versions / search plugins | references/discovering-plugins.md |
| Install or update a plugin (latest or a pinned version) | references/installing-plugins.md |
| "What plugins are installed?" / remove an installed plugin | references/managing-installed-plugins.md |
| Publish / upload / release a plugin to the catalog | references/publishing-plugins.md |
Prerequisites
- Read the base
jfrogskill first.../jfrog/SKILL.mdowns the shared guards this skill depends on, so this skill does not repeat them — follow them there:- The environment check — confirm
jfis installed before the firstjfcall, and install it if missing. - The server selection rules
— resolve the default
<SID>once and reuse it, pass--server-id <SID>after the subcommand on everyjfcall, and use one server per request. Resolve it now, before anyjfcall:jf config show 2>/dev/null \ | awk '/^Server ID:/{id=$NF} /^Default:[[:space:]]*true/{print id; exit}' # stdout: the default server-id; if empty, stop and ask which server to use - The stop-on-error rule — on any
jffailure, stop and never switch servers.
- The environment check — confirm
What ships with it
8 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.
- references/discovering-plugins.md 3.3 KB
- references/discovering-skills.md 3.2 KB
- references/installing-plugins.md 6.0 KB
- references/installing-skills.md 8.3 KB
- references/managing-installed-plugins.md 3.9 KB
- references/managing-installed-skills.md 2.9 KB
- references/publishing-plugins.md 9.1 KB
- references/publishing-skills.md 10 KB
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.
- 7d ago First seen · 131 lines · 110 tokens per session scan C 5ce59ec683b4
jfrog-ai-catalog is a skill published in the GitHub repository jfrog/claude-plugin (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 110 tokens to every session and 1,870 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to jfrog-ai-catalog, differing in 0 lines, and is treated as a copy.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…