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/alexmond/jhelm/jacoconpx skills add alexmond/jhelm --skill jacocogit clone --depth 1 https://github.com/alexmond/jhelmWhat 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.00013 | $0.01965 |
| Opus 5 | $0.00006 | $0.00983 |
| Sonnet 5 | $0.00003 | $0.00393 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
jacoco 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 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.
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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check JaCoCo Code Coverage
Run verify to generate coverage reports, then parse and display results.
Minimum threshold: 80% line coverage
Step 1: Generate coverage reports
Specific module (e.g., /jacoco jhelm-core):
./mvnw verify -pl $ARGUMENTS -q
All modules:
./mvnw verify -q
Step 2: Module-level summary
Shows coverage percentage per module with PASS/FAIL status:
python3 -c "
import xml.etree.ElementTree as ET
THRESHOLD = 80
modules = ['jhelm-gotemplate', 'jhelm-core', 'jhelm-cli']
if '$ARGUMENTS':
modules = ['$ARGUMENTS']
print(f'{'Module':<20} {'Covered':>8} {'Total':>8} {'Coverage':>10} {'Status':>8}')
print('-' * 58)
for module in modules:
try:
tree = ET.parse(f'{module}/target/site/jacoco/jacoco.xml')
root = tree.getroot()
for counter in root.findall('counter'):
if counter.get('type') == 'LINE':
missed = int(counter.get('missed'))
covered = int(counter.get('covered'))
total = missed + covered
pct = covered / total * 100 if total > 0 else 0
status = 'PASS' if pct >= THRESHOLD else 'FAIL'
print(f'{module:<20} {covered:>8} {total:>8} {pct:>9.2f}% {status:>8}')
except FileNotFoundError:
print(f'{module:<20} {'N/A':>8} {'N/A':>8} {'N/A':>10} {'MISSING':>8}')
"
Step 3: Class-level breakdown (lowest coverage first)
Find classes with lowest coverage to target improvements:
python3 -c "
import xml.etree.ElementTree as ET
module = '$ARGUMENTS' if '$ARGUMENTS' else 'jhelm-gotemplate'
tree = ET.parse(f'{module}/target/site/jacoco/jacoco.xml')
root = tree.getroot()
results = []
for pkg in root.findall('.//package'):
for cls in pkg.findall('class'):
for counter in cls.findall('counter'):
if counter.get('type') == 'LINE':
missed = int(counter.get('missed'))
covered = int(counter.get('covered'))
total = missed + covered
if total > 0:
pct = covered / total * 100
results.append((pct, missed, covered, total, cls.get('name')))
results.sort()
print(f'{'Coverage':>10} {'Missed':>8} {'Covered':>8} {'Total':>8} Class')
print('-' * 80)
for pct, missed, covered, total, name in results:
print(f'{pct:>9.1f}% {missed:>8} {covered:>8} {total:>8} {name}')
"
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 · 225 lines · 13 tokens per session scan A 9db7fd254f57
jacoco is a skill published in the GitHub repository alexmond/jhelm (4 stars, last pushed 9d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,965 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.
Other skills, from other repositories
evergreen
Evergreen CI infrastructure, configuration validation. Use when modifying .evergreen/ config, preparing to submit changes or understanding the Evergreen test matrix.
sync-agents-docs
Sync AGENTS.md files, skills, and references after buildSrc or convention changes. Use after modifying build plugins, formatting rules, testing conventions, or task names to keep documentation consistent.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.