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-delete-projectnpx skills add jfrog/ai-agent-examples --skill jfrog-delete-projectgit 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-delete-project)<a href="https://agentmods.dev/skills/jfrog/ai-agent-examples/jfrog-delete-project"><img src="https://agentmods.dev/badge/skills/jfrog/ai-agent-examples/jfrog-delete-project.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.00043 | $0.04000 |
| Opus 5 | $0.00022 | $0.02000 |
| Sonnet 5 | $0.00009 | $0.00800 |
| Haiku 4.5 | $0.00004 | $0.00400 |
Grade B, and why
jfrog-delete-project scanned grade B with 2 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| curl | `brew install curl` | `sudo apt-get install curl` | 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delete JFrog Project
Prefer jf api (../../../platform-features/skills/jfrog-cli/jf-api-patterns.md); curl is fallback where shown.
This skill safely deletes a JFrog project and handles its associated repositories. Repos that are shared with other projects are unassigned (preserved) instead of deleted. It includes multiple confirmation steps and cross-project checks to prevent accidental data loss.
Trigger Phrases
Activate this skill when the user says things like:
- "Delete JFrog project"
- "Remove JFrog project"
- "Clean up JFrog project"
- "Delete project from JFrog"
Required Tools
Before proceeding, verify these tools are installed:
# Check required tools
for tool in curl jq; do
if ! command -v $tool &> /dev/null; then
echo "ERROR: $tool is not installed"
else
echo "OK: $tool is installed"
fi
done
Installation if missing:
| Tool | macOS | Ubuntu/Debian |
|---|---|---|
| curl | brew install curl |
sudo apt-get install curl |
| jq | brew install jq |
sudo apt-get install jq |
Deletion Workflow
Step 1: Load Credentials
Load credentials from .env (or environment variables):
# Load .env if vars are not already set
if [ -z "$JFROG_URL" ] || [ -z "$JFROG_ACCESS_TOKEN" ]; then
if [ -f .env ]; then
set -a; source .env; set +a
fi
fi
# Verify vars are set
if [ -z "$JFROG_URL" ] || [ -z "$JFROG_ACCESS_TOKEN" ]; then
echo "ERROR: JFROG_URL and JFROG_ACCESS_TOKEN must be set (in environment or .env file)"
exit 1
fi
echo "Found credentials for: ${JFROG_URL}"
If credentials are missing, prompt the user:
I need to connect to your JFrog Platform. Please provide:
- JFrog Platform URL (e.g.,
https://mycompany.jfrog.io)- Access Token (with admin privileges)
Validate the token:
- Check authentication is valid:
jf api /artifactory/api/system/version
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.
- 4d ago First seen · 439 lines · 43 tokens per session scan B 999bdf107d94
jfrog-delete-project is a skill published in the GitHub repository jfrog/ai-agent-examples (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 4,000 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, 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…