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/alexmskills/jacoconpx skills add alexmond/alexmskills --skill jacocogit clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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/alexmond/alexmskills/jacoco)<a href="https://agentmods.dev/skills/alexmond/alexmskills/jacoco"><img src="https://agentmods.dev/badge/skills/alexmond/alexmskills/jacoco.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.1 | $0.00075 | $0.02343 |
| Opus 5 | $0.00037 | $0.01171 |
| Sonnet 5 | $0.00015 | $0.00469 |
| Haiku 4.5 | $0.00007 | $0.00234 |
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 6d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check JaCoCo Code Coverage
Try it:
/maven-quality:jacoco payment-service— or say "what's our test coverage on the payment service?".
Run verify to generate coverage reports, then parse and display the results.
Defaults target a Maven/Java project with the JaCoCo plugin bound so that
verify produces target/site/jacoco/jacoco.xml.
Coverage gate: 80% line coverage (default)
Adjust THRESHOLD in the snippets below to match your project's gate.
Adjusting for your project
- Maven invocation: examples use the wrapper
./mvnw. If your environment has no wrapper, substitute yourmvnbinary, e.g.bash "/path/to/mvn" verify -f pom.xml -q. - Single module / non-modular project: the report lives at
target/site/jacoco/jacoco.xml. Setmodules = ['.']and use'.'/target/...paths, or just drop themoduleprefix. - Multi-module project: set the
moduleslist to your module directory names, or pass one module as the argument to scope to it. $ARGUMENTS(when present) is treated as either a module name (Steps 1, 2, 5, 7) or a class source-file name (Step 4).
Step 1: Generate coverage reports
Specific module (e.g. argument = my-core):
./mvnw verify -pl $ARGUMENTS -q
All modules / whole project:
./mvnw clean verify -q
Step 2: Module-level summary (PASS/FAIL vs gate)
python3 -c "
import xml.etree.ElementTree as ET
THRESHOLD = 80
# Adjust to your module directory names, or use ['.'] for a single-module project.
modules = ['module-a', 'module-b', 'module-c']
if '$ARGUMENTS':
modules = ['$ARGUMENTS']
print(f'{\"Module\":<24} {\"Covered\":>8} {\"Total\":>8} {\"Coverage\":>10} {\"Status\":>8}')
print('-' * 62)
for module in modules:
path = f'{module}/target/site/jacoco/jacoco.xml' if module != '.' else 'target/site/jacoco/jacoco.xml'
try:
root = ET.parse(path).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:<24} {covered:>8} {total:>8} {pct:>9.2f}% {status:>8}')
except FileNotFoundError:
print(f'{module:<24} {\"N/A\":>8} {\"N/A\":>8} {\"N/A\":>10} {\"MISSING\":>8}')
"
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.
- 6d ago First seen · 224 lines · 75 tokens per session scan A e50e08ca88db
jacoco is a skill published in the GitHub repository alexmond/alexmskills (6 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 2,343 once invoked, about $0.0004 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
test-fixing
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.