jfrog-platform-conventions

Naming and setup rules for JFrog Platform templates, rules, policies, and projects. They define naming formats, encourage reuse, and specify the order for creating policy components.

In plain words
What is it for?
Use it when creating or managing JFrog templates, rules, policies, or project-scoped lifecycle controls.
Why use it?
It helps keep JFrog configuration consistent and prevents policies from being created in the wrong sequence or outside the intended project.

Cursor rule

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.

agentmods
npx agentmods add rules/jfrog/ai-agent-examples/jfrog-platform-conventions
Clone the repo
git clone --depth 1 https://github.com/jfrog/ai-agent-examples
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 398 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00398
Opus 5 $0.00005 $0.00199
Sonnet 5 $0.00002 $0.00080
Haiku 4.5 $0.00001 $0.00040

Measured 2d ago against content hash f888c20d1bed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

jfrog-platform-conventions 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 2d 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.

compliance-and-policies/skills/apptrust-evidence-policies/rules/jfrog-platform-conventions.mdc · 35 lines

What it actually says

JFrog Platform Conventions

  • Always create and manage policies within a JFrog Project unless the user explicitly opts out.
  • templates, rules and policies name format: 2-32 lowercase alphanumeric characters, must start with a letter.
  • templates, rules and policies description format: 2-100 alphanumeric characters, must start with a letter.
  • Prefer using existing templates, rules and policies
  • Create policies in this order: template, rules, then policy.

Help Documentation references

Templates references: list templates get tempalte create template update template delete template

Rules references: list rules get rule create rule update rule delete rule

Policies references: list policies create policy get policy update policy delete policy

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.

  1. 2d ago First seen · 35 lines · 10 tokens per session scan A f888c20d1bed

Subscribe to this mod's changes

jfrog-platform-conventions is a cursor rule published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 398 once invoked, about $0.0001 per session on Opus 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.