Borrowing it
Nothing to install: this file belongs to eclipse-rdf4j/rdf4j. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eclipse-rdf4j/rdf4j/main/.agent/skills/docker-jfr-benchmark-loop/SKILL.mdgit clone --depth 1 https://github.com/eclipse-rdf4j/rdf4jWrote 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/eclipse-rdf4j/rdf4j/docker-jfr-benchmark-loop)<a href="https://agentmods.dev/skills/eclipse-rdf4j/rdf4j/docker-jfr-benchmark-loop"><img src="https://agentmods.dev/badge/skills/eclipse-rdf4j/rdf4j/docker-jfr-benchmark-loop/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.
<a href="https://agentmods.dev/skills/eclipse-rdf4j/rdf4j/docker-jfr-benchmark-loop"><img src="https://agentmods.dev/badge/skills/eclipse-rdf4j/rdf4j/docker-jfr-benchmark-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.00949 |
| Opus 5 | $0.00051 | $0.00475 |
| Sonnet 5 | $0.00020 | $0.00190 |
| Haiku 4.5 | $0.00010 | $0.00095 |
Grade A, and why
docker-jfr-benchmark-loop 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker JFR Benchmark Loop
Use this skill for one-benchmark perf work in this repo. Default runner: scripts/run-docker-jfr-loop.sh, not ad hoc Maven or raw JMH commands.
Quick start
Dry-run a known selector:
.codex/skills/docker-jfr-benchmark-loop/scripts/run-docker-jfr-loop.sh \
org.eclipse.rdf4j.model.benchmark.ValueCreationBenchmark.createBNode \
--dry-run
Explicit selector plus params:
.codex/skills/docker-jfr-benchmark-loop/scripts/run-docker-jfr-loop.sh \
--module core/model \
--class org.eclipse.rdf4j.model.benchmark.ValueCreationBenchmark \
--method createBNode \
--param samples=1000
Repo-grounded defaults
- The wrapper calls repo helper
scripts/run-single-benchmark-docker.sh. - The Docker helper already forces Linux Java 26 plus
--enable-jfr --enable-jfr-cpu-times. - The inner helper already enforces:
settings=profiledumponexit=trueduration=120swarmup=0measurement=10iterations of10sforks=1jdk.CPUTimeSample#enabled=truereport-on-exit=cpu-time-hot-methods
- This skill wrapper adds the missing fidelity flags:
-XX:FlightRecorderOptions=stackdepth=1024,samplethreads=true-XX:+UnlockDiagnosticVMOptions-XX:+DebugNonSafepoints
Core loop
- Pick one benchmark selector. Keep selector, params, Docker image, and profiling flags constant for the whole comparison.
- Capture a baseline run with
scripts/run-docker-jfr-loop.sh. - Read the
.jfrusing references/jfr-reading.md. - Choose one candidate fix with material CPU share. Prefer the fix most likely to move total runtime, not just local self time.
- Re-run the exact same selector and params.
- Compare benchmark delta plus hotspot shift.
- Repeat until:
- the hotspot shifts,
- CPU share falls below a meaningful threshold,
- or GC / locks / memory / I/O / JIT behavior dominates instead.
Operating rules
- Route benchmark variation through
--param. - Route JVM tuning through
--jvm-arg. - Do not use raw
--jmh-argduring JFR runs; the helper rejects extra JMH args when JFR is enabled. - Do not switch to a second
StartFlightRecording; stay aligned with repo helper behavior. - Do not treat a small benchmark gain as proof the hotspot fix failed. First check whether another bottleneck surfaced and now caps the total speedup.
- If the run is not CPU-bound, say so and pivot to lock, GC, memory, I/O, or JIT evidence instead of forcing a CPU-only story.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 91 lines · 101 tokens per session scan A c754aa35b705
docker-jfr-benchmark-loop is a skill published in the GitHub repository eclipse-rdf4j/rdf4j (412 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 101 tokens to every session and 949 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
open-ontologies
AI-native ontology engineering using 50+ MCP tools backed by an in-memory Oxigraph triple store. Build, validate, query, and govern RDF/OWL ontologies with a generate-validate-iterate loop. Use when building ontologies, knowledge graphs, RDF data, SPARQL queries, BORO/4D modeling, SHACL validation, clinical…
mcp-sparql
Exposes SPARQL query capabilities to LLMs via the Model Context Protocol. Supports SELECT, ASK, CONSTRUCT, and DESCRIBE queries against any SPARQL endpoint.
knowledge-graph-sparql
Knowledge graph construction, SPARQL querying, and entity linking for library and research data management using RDF and Wikidata.
aws-cloudformation-ecs
Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS…
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
706-technologies-containers-docker
Use when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime distributions such as Alpaquita, JVM container ergonomics, non-root execution, image metadata, .dockerignore, reproducible builds, vulnerability…