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-reference-architecturenpx skills add jfrog/claude-plugin --skill jfrog-reference-architecturegit 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-reference-architecture)<a href="https://agentmods.dev/skills/jfrog/claude-plugin/jfrog-reference-architecture"><img src="https://agentmods.dev/badge/skills/jfrog/claude-plugin/jfrog-reference-architecture.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 | $0.00165 | $0.02139 |
| Opus 5 | $0.00082 | $0.01069 |
| Sonnet 5 | $0.00033 | $0.00428 |
| Haiku 4.5 | $0.00016 | $0.00214 |
Grade A, and why
jfrog-reference-architecture 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 3d 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.
This is a copy
100% identical to jfrog-reference-architecture — 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog Reference Architecture
Planning skill for topology, sizing, and deployment. Answers must come from live fetches of the JFrog Platform Reference Architecture — not from training data or duplicated tables in this repo.
Prerequisites
- Read
../jfrog/SKILL.mdfor JFrog Platform concepts, product vocabulary, and routing to other workflows. - No
jfCLI required for planning-only questions (no live instance needed).
Source of truth
| Allowed in this skill | Not allowed |
|---|---|
| Fetch procedures, workflows, output templates | Sizing RPM tables, use-case narratives, deployment checklists copied from the site |
| Helm chart preference (jfrog-platform on Kubernetes) | Hardcoded slug lists or criteria |
Every factual claim (numbers, template names, limitations, infrastructure guidance) must come from a WebFetch in the current session. If fetch fails, retry or ask the user to open the URL — do not guess from memory.
Citations: Use the URL: line from the relevant section in the fetched content (public HTML URL). You may note content was read from llms-full.txt.
For fetch URLs, size thresholds, and the fallback ladder, see references/doc-access.md.
Gotchas
| Symptom | Mitigation |
|---|---|
| Sizing numbers or use-case names not on the official site | WebFetch ref-arch first; cite URL: from the fetch — not training data |
small template recommended for production |
Re-read production warnings in the fetched Artifactory/Xray sizing sections |
| SaaS section missing or 404 | SaaS paths use prefix jfrog-saas, not saas |
| HA storage guidance wrong | Per ref arch: cluster-file-system or object storage — not file-system for HA |
WebFetch blocked, truncated, or over size limits |
Request full_network; downgrade per references/doc-access.md |
Session bootstrap
What ships with it
1 file 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.
- 3d ago First seen · 156 lines · 165 tokens per session scan A 001a522d849a
jfrog-reference-architecture is a skill published in the GitHub repository jfrog/claude-plugin (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 165 tokens to every session and 2,139 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to jfrog-reference-architecture, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
huggingface-spaces
Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't…
ondb
A logical analysis and reasoning tool for AI. Use when decomposing documents into structured knowledge, querying entities and relations, validating consistency, or indexing files. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", "analyze this document", entity CRUD, or cross-skill…
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…