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-patternsgit 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-patterns)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/jfrog-patterns"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-patterns/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-patterns"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-patterns.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.00106 | $0.02030 |
| Opus 5.5 | $0.00042 | $0.00812 |
| Sonnet 5.5 | $0.00021 | $0.00406 |
| Haiku 4.5 | $0.00011 | $0.00203 |
Grade A, and why
JFrog Patterns scanned grade A with 0 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog Patterns Skill
Authentication
This skill does not call JFrog APIs directly. Use the product skills (jfrog-artifactory, jfrog-access, jfrog-security, jfrog-distribution, jfrog-curation, jfrog-workers) for authentication and API/CLI usage when implementing a pattern.
What Are Patterns?
Patterns are recommended architectural setups for the JFrog Platform. Each pattern describes:
- What problem it solves and the architecture
- JFrog concepts involved (repos, policies, builds, etc.)
- Difficulty level (SIMPLE -> INTERMEDIATE -> ADVANCED)
- What gets created when the setup wizard runs (repos, policies, watches, projects)
- Which skills to use for API/CLI implementation
Pattern Catalog (22 patterns in 6 categories)
| Category | Patterns | Levels |
|---|---|---|
| CI Integration | 4 patterns | SIMPLE to ADVANCED |
| Repositories | 3 patterns | SIMPLE to ADVANCED |
| Supply Chain Security | 4 patterns | INTERMEDIATE to ADVANCED |
| Release Lifecycle | 4 patterns | SIMPLE to ADVANCED |
| Multi-Site Architecture | 5 patterns | All ADVANCED |
| AppTrust | 2 patterns | Both SIMPLE |
Which Pattern Should I Use?
Use the 5 user journeys to pick the right patterns. See journeys.md for the full guide.
| If your goal is... | Start with... |
|---|---|
| Centralize artifacts and automate CI/CD | CI Integration + Basic Repo Setup |
| Secure the software supply chain | Xray Security + Curation Security |
| Accelerate developer productivity | CI Integration + Curation + Contextual Analysis |
| Handle enterprise-scale multi-site | Multi-Site Active/Active or Active/Standby |
| Govern releases with compliance | Release Lifecycle + Evidence + AppTrust |
| Deploy trusted AI models | Journey 5 in journeys.md |
Difficulty Progression
Start at SIMPLE, build up:
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.
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 · 143 lines · 106 tokens per session scan A 05fcbc0c2409
JFrog Patterns is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 2,030 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…