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/detect-existing-patternsnpx skills add jfrog/ai-agent-examples --skill detect-existing-patternsgit 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/detect-existing-patterns)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/detect-existing-patterns"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/detect-existing-patterns.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.00057 | $0.02808 |
| Opus 5 | $0.00028 | $0.01404 |
| Sonnet 5 | $0.00011 | $0.00562 |
| Haiku 4.5 | $0.00006 | $0.00281 |
Grade A, and why
detect-existing-patterns 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Prefer **`jf api`** per [../../../platform-features/skills/jfrog-cli/jf-api-patterns.md](../../../platform-features/skills/jfrog-cli/jf-api-patterns.md) after `jf config` and platform confirmation. Examples below use **` How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detect Existing Naming Patterns
Queries the JFrog Platform for existing projects and repositories, analyzes their naming conventions, and presents the user with a choice between the detected pattern and the standard onboarding pattern.
API transport
Prefer jf api per ../../../platform-features/skills/jfrog-cli/jf-api-patterns.md after jf config and platform confirmation. Examples below use curl as fallback.
Inputs
JFROG_URL-- Platform base URL (forcurlfallback; derive fromjf config showwhen using CLI)JFROG_ACCESS_TOKEN-- Admin token (forcurlfallback only)new_project_key-- the project key about to be onboarded (used to generate examples)new_ecosystems-- list of ecosystems for the new project (used to generate examples)state_project_key-- (optional) the state/system project key to exclude from analysis (default:system)
Output
A naming_pattern object with these fields (passed to jfrog-create-repos):
| Field | Type | Description | Default (standard) |
|---|---|---|---|
separator |
string | Character between name components | - |
virtual_suffix |
string | Type label for virtual repos; empty string means no suffix | "" (no suffix) |
type_map |
object | Maps logical types to their name tokens | {"local": "local", "remote": "remote"} |
eco_map |
object | Maps manifest ecosystem names to repo name tokens (only entries that differ from the identity mapping) | {"pip": "pypi"} |
The standard (default) pattern produces names like {key}-npm-local, {key}-npm-remote, {key}-npm.
When to Skip
- If the platform has no existing projects (or only the state project), skip detection entirely and use the standard pattern. Do not ask the user anything.
- If no repos can be found across existing projects, skip detection and use the standard pattern.
Workflow
0. Load credentials
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 · 293 lines · 57 tokens per session scan A 2aaef1edd6c9
detect-existing-patterns is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 2,808 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…