What is onboarding-workflow?

A set of rules for coordinating the steps used to onboard several projects into JFrog Platform, a service for storing and managing software packages.

It guides detection of existing naming patterns, project provisioning, repository creation, optional Xray and Curation settings, and member setup.

It keeps project creation, repository setup, indexing, security checks, and membership changes in a consistent order.

onboarding-workflow — Cursor rule for Cursor by jfrog

Install

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.

Clone the repo

git clone --depth 1 https://github.com/jfrog/ai-agent-examples

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/jfrog/ai-agent-examples/onboarding-workflow/github.svg)](https://agentmods.dev/rules/jfrog/ai-agent-examples/onboarding-workflow)

Your own site

<a href="https://agentmods.dev/rules/jfrog/ai-agent-examples/onboarding-workflow"><img src="https://agentmods.dev/badge/rules/jfrog/ai-agent-examples/onboarding-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/jfrog/ai-agent-examples/onboarding-workflow"><img src="https://agentmods.dev/badge/rules/jfrog/ai-agent-examples/onboarding-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,012 This file is loaded in full into every session.

When invoked 4,012 The same file — it is already loaded in full.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.04012	$0.04012
Opus 5.5	$0.01605	$0.01605
Sonnet 5.5	$0.00802	$0.00802
Haiku 4.5	$0.00401	$0.00401

Measured 2mo ago against content hash d5a0d914d287, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

onboarding-workflow 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 2mo 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.

When a local manifest file is found (e.g., `jfrog-manifest.yaml`), **always compare** its `jfrog.url` value against the **URL of the JFrog instance the user confirmed** from `jf config show` (or against `$JFROG_URL` from

onboarding-workflows/rules/onboarding-workflow.mdc · 218 lines

How it starts

The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Onboarding Workflow Guidance

Skill Chain Order

Always follow this sequence when onboarding a project:

Pre-project step (run once before any projects): 0. Detect existing patterns -- after prerequisites pass, query the platform for existing projects and repositories via the detect-existing-patterns skill. If existing naming patterns are found that differ from the standard convention, present both the detected and standard options with concrete examples and let the user choose. The chosen naming_pattern applies to all projects in the current onboarding run. If the platform is empty or existing repos already follow the standard pattern, skip the question and use the standard pattern.

Per-project steps (repeat for each project in the manifest):

Provision project -- create JFrog project if it does not exist
Create repositories -- from ecosystems (auto-generated trios), custom repositories list, or both (smart merge); conditionally enable Xray indexing and Curation (curated: true flag) based on manifest settings. Pass the naming_pattern from step 0 to control how ecosystem-generated repo names are constructed.
Add members -- users and groups with appropriate roles
OIDC setup -- configure OIDC provider and identity mappings (controlled by github.oidc_setup in manifest; if true and subscription does not support it, abort)
Configure package managers -- update configs in the GitHub repos for local dev
Configure CI workflows -- modify GitHub Actions for Artifactory integration (uses OIDC if github.oidc_setup: true, otherwise secrets-based auth)

Post-project steps (run once after all projects): 7. Curation policies -- if any project has curation.enabled: true, invoke jfrog-curation-onboarding in automated mode to create the 8 standard curation policies (Block Malicious + 7 dry-run). Uses all_repos scope when all projects have curation enabled, or specific_repos scope when only some do. Notification email comes from jfrog.curation.notification_email (or per-project override). 8. Persist manifest -- store final manifest to the configured state backend (Artifactory or git)

Read the full file on GitHub · 218 lines

Changes

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.

2mo ago First seen · 218 lines · 4,012 tokens per session scan A d5a0d914d287

Subscribe to this mod's changes

onboarding-workflow is a cursor rule published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 4,012 tokens to every session, about $0.0160 per session on Opus 5.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.

Project management

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

onboarding-workflow