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-curation-onboardingnpx skills add jfrog/ai-agent-examples --skill jfrog-curation-onboardinggit 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-curation-onboarding)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/jfrog-curation-onboarding"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-curation-onboarding.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.00098 | $0.06619 |
| Opus 5 | $0.00049 | $0.03309 |
| Sonnet 5 | $0.00020 | $0.01324 |
| Haiku 4.5 | $0.00010 | $0.00662 |
Grade A, and why
jfrog-curation-onboarding 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)); **`curl`** is **fallback** where shown. How it starts
The opening of the file, as written. The whole thing — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog Curation Onboarding
Prefer jf api (../../../platform-features/skills/jfrog-cli/jf-api-patterns.md); curl is fallback where shown.
Sets up JFrog Curation protection on an existing JFrog Platform instance by verifying Curation is enabled and creating a set of security, license, and operational risk policies across remote repositories. Malicious packages are blocked; all other policy violations are logged in dry-run mode with email notifications.
Trigger Phrases
Activate this skill when the user says things like:
- "Setup curation with my jfrog"
- "Onboard jfrog curation"
- "Connect my jfrog with curation"
- "Enable curation protection"
- "Block malicious packages"
Operating Modes
This skill has two operating modes:
Standalone Mode (Interactive)
Triggered directly by the user. Runs the full interactive workflow: prerequisite checks, repo discovery, email collection, scope selection, user confirmation, policy creation, and verification. This is the default mode described in the sections below.
Automated Mode (Manifest-Driven)
Called by the jfrog-project-onboarding orchestrator when curation.enabled resolves to true for one or more projects. In this mode the skill:
- Skips prerequisite checks (Steps 0-1b) -- already verified by the orchestrator
- Skips interactive email collection (Step 4) -- uses
notification_emailfrom the manifest - Skips interactive scope selection and user confirmation (Step 5) -- the orchestrator already collected confirmation
- Executes Steps 2 (check curation status), 3 (discover repos), 6 (enable curation on repos), 7 (create policies), 8 (verify), and 9 (report)
Automated Mode Inputs
| Input | Source | Description |
|---|---|---|
CURATED_REMOTE_REPOS |
Orchestrator | JSON array of remote repo keys from all curation-enabled projects (e.g., ["proj-npm-remote", "proj-pypi-remote"]) |
CURATION_NOTIFY_EMAIL |
Manifest jfrog.curation.notification_email (or per-project override) |
Email for policy violation notifications |
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 · 531 lines · 98 tokens per session scan A fe61d30253d3
jfrog-curation-onboarding is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 6,619 once invoked, about $0.0005 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
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…