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/aviatesk/jetls.jl/run-testnpx skills add aviatesk/JETLS.jl --skill run-testgit clone --depth 1 https://github.com/aviatesk/JETLS.jlWrote 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/aviatesk/jetls.jl/run-test)<a href="https://agentmods.dev/skills/aviatesk/jetls.jl/run-test"><img src="https://agentmods.dev/badge/skills/aviatesk/jetls.jl/run-test.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.00036 | $0.00399 |
| Opus 5 | $0.00018 | $0.00199 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
run-test 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.
What it actually says
Run JETLS tests
Use this skill when you need to validate JETLS changes with tests or decide which test command to run.
Choose the narrowest useful test
When you changed a specific component, run the component-specific test instead of the full test suite.
Use this standard form:
julia --startup-file=no --project=test -e 'using Test; @testset "test_XXX" include("test/test_XXX.jl")'
Notes:
--startup-file=noavoids loading unnecessary startup utilities.--project=testenablesJETLS_TEST_MODEfor proper test execution.
Focused iteration with TestRunner.jl
For faster iteration on a specific @testset,
use TestRunner.jl
when testrunner --help succeeds:
testrunner --project=test test/test_XXX.jl "testset_name"
TestRunner.jl is still experimental, but it is reliable enough to try first
when the target @testset is clear. If it fails in a way that looks specific
to TestRunner.jl, fall back to running the test file standalone.
Avoid the full suite by default
Pkg.test() takes about 3.5 minutes as of June 2026. Avoid it unless:
- Changes affect multiple components.
- The user explicitly requests the full test suite.
- You are unsure which narrower tests are relevant.
Reporting
In the final response, report the exact test command you ran and whether it passed, failed, or timed out. If you skipped tests, explain why.
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 · 56 lines · 36 tokens per session scan A 4f396148572c
run-test is a skill published in the GitHub repository aviatesk/JETLS.jl (306 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 399 once invoked, about $0.0002 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-30.
Other skills, from other repositories
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
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.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
review-usability
Check whether the common Python code an LLM would plausibly write still works on this branch, testing real cases in ./playground against CPython. Use to find behaviour that diverges from CPython or trips up ordinary idiomatic code.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…