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 rules/jfrog/ai-agent-examples/jfrog-cli-platform-apigit clone --depth 1 https://github.com/jfrog/ai-agent-examplesWhat 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.00688 | $0.00688 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
jfrog-cli-platform-api 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 yesterday.
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.
## Fallback to `curl` How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JFrog CLI and jf api (preferred)
Minimum version
- Use JFrog CLI 2.100.0 or newer (
jf --version). Thejf apicommand requires this version. - Install or upgrade from Install JFrog CLI.
Before any JFrog Platform API work
- Ensure
jfis installed and meets the version requirement. - Ensure a server is configured using the login-flow in platform-features/skills/jfrog-cli/login-flow.md:
jf config show,jf config add, or web login. - Platform confirmation (wrong-instance guard): After the active server is known (or chosen when several exist), show the platform URL(s) from
jf config show(server id and URL for each). Ask the user to confirm this is the correct JFrog instance, or to switch (jf config use, add another server, etc.). When only one server exists, still show its URL once for confirmation (compare to manifestjfrog.urlwhen applicable). Ask one question at a time (see global/rules/interaction-questions.mdc). - Post-confirmation readiness: Only after the user confirms, run
jf api /artifactory/api/v1/system/readinesswith the same--server-idas the confirmed config (or the default server if none specified). On failure, stop and troubleshoot URL/credentials before other API work.
Preferred invocation
- Use
jf api <path>for JFrog REST paths (path only, e.g./access/api/v2/users,/artifactory/api/repositories). Base URL and credentials come fromjf config. - Use
--server-id=<id>when multiple configurations exist or after the user picks a server.
Fallback to curl
Use curl with $JFROG_URL and Authorization: Bearer $JFROG_ACCESS_TOKEN only when:
- The CLI is missing or below 2.100.0, or
- The user explicitly operates without
jf config, or - A documented bootstrap step requires
curl(e.g. web-login session registration before config exists).
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.
- yesterday First seen · 39 lines · 688 tokens per session scan A 030d8c212bdf
jfrog-cli-platform-api 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 688 tokens to every session, about $0.0034 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.