creating-julia-test-env

creating-julia-test-env is a skill for Claude Code, Codex from hashgraph-online/awesome-codex-plugins. It costs 14 tokens per session (518 once invoked), scanned A, original, Apache-2.0.

A setup guide for adding tests to a Julia package, which is reusable Julia code organized for distribution. It creates a separate test environment and connects it to the package.

In plain words
What is it for?
It sets up the test folder, test project file, package workspace or compatibility settings, local package development, and sample tests.
Why use it?
It gives tests their own dependencies and a repeatable way to run against the local package.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It sets up the test folder, test project file, package workspace or compatibility settings, local package development, and sample tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hashgraph-online/awesome-codex-plugins/creating-julia-test-env
About the project

Awesome Codex Plugins is a curated catalogue and marketplace of installable plugins, skills, and related resources for OpenAI Codex and ChatGPT. It helps people find, create, validate, and submit extensions for Codex workflows across its app, command-line interface, and IDE extensions. The catalogue add-ons are the plugins, skills, agents, and hooks listed or supported by this project.

hashgraph-online/awesome-codex-plugins · 1,397 stars · on GitHub · hol.org

Install

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.

Any agent
npx skills add hashgraph-online/awesome-codex-plugins --skill creating-julia-test-env
Clone the repo
git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for creating-julia-test-env

README.md
[![agentmods](https://agentmods.dev/badge/skills/hashgraph-online/awesome-codex-plugins/creating-julia-test-env/github.svg)](https://agentmods.dev/skills/hashgraph-online/awesome-codex-plugins/creating-julia-test-env)
Your own site
<a href="https://agentmods.dev/skills/hashgraph-online/awesome-codex-plugins/creating-julia-test-env"><img src="https://agentmods.dev/badge/skills/hashgraph-online/awesome-codex-plugins/creating-julia-test-env/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.

agentmods 80×15 button for creating-julia-test-env

Your own site · 80×15
<a href="https://agentmods.dev/skills/hashgraph-online/awesome-codex-plugins/creating-julia-test-env"><img src="https://agentmods.dev/badge/skills/hashgraph-online/awesome-codex-plugins/creating-julia-test-env.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00518
Opus 5.5 $0.00006 $0.00207
Sonnet 5.5 $0.00003 $0.00104
Haiku 4.5 $0.00001 $0.00052

Measured 1mo ago against content hash 6beb88223d51, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

creating-julia-test-env 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 1mo 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.

plugins/AtelierArith/atelier-arith-julia-development-skills/skills/creating-julia-test-env/SKILL.md · 89 lines

What it actually says

creating-julia-test-env

A minimal Julia package layout looks like this:

$ tree
.
├── Project.toml
└── src
    └── MyPkg.jl # Assume the package is named MyPkg for this example.

To add software tests for this package, follow the steps below.

Step 1: Create the test directory, runtests.jl, and a Project.toml for the test environment.

mkdir test
touch test/runtests.jl
touch test/Project.toml

Step 2: Add a [workspace] section to ./Project.toml (not test/Project.toml):

name = "MyPkg"

...
...<omitted>
...

# Add this section
[workspace]
projects = ["test"]

Note: If you are on Julia 1.11 or older, do not use [workspace]. Instead, add [extras] and [targets]:

[extras]
Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40"

[targets]
test = ["Test"]

Step 3: Set up ./test/Project.toml as follows:

$ cd test
$ ls
runtests.jl Project.toml
$ julia --project -e 'using Pkg; Pkg.add("Test")'
$ julia --project -e 'using Pkg; Pkg.develop(path="../")'
$ cat Project.toml
[deps]
MyPkg = <UUID for MyPkg goes here>
Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40"

[sources]
MyPkg = {path = ".."}

Step 4: Put a simple sample test in test/runtests.jl (replace MyPkg with your actual package name).

using Test

using MyPkg

@testset "sample" begin
    @test 1 + 1 == 2
end

Step 5: Run the following to verify:

$ julia --project -e 'using Pkg; Pkg.test()'
Changes

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.

  1. 1mo ago First seen · 89 lines · 14 tokens per session scan A 6beb88223d51

Subscribe to this mod's changes

creating-julia-test-env is a skill published in the GitHub repository hashgraph-online/awesome-codex-plugins (1,397 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

awesome-chatgpt

Search this repository's awesome-ChatGPT-repositories list for open-source ChatGPT and LLM projects such as RAG frameworks, agents, chatbots, CLIs, prompts, and browser extensions. Use when the user asks to find tools, libraries, or repos related to ChatGPT, LLMs, or AI development; not for editing or adding list…

taishi-i/awesome-ChatGPT-repositories · 79 tokens

awesome-chatgpt-search

Search 2500+ curated ChatGPT and LLM open-source repositories. Use when the user asks to find tools, libraries, or repos related to ChatGPT, LLMs, RAG, agents, langchain, NLP, AI development, or any open-source AI tooling.

taishi-i/awesome-ChatGPT-repositories · 63 tokens

tdd-test-engineer

Use for test-first development, regression tests, flaky test debugging, coverage gaps, test strategy, CI failures, or converting bugs into minimal reproducible tests.

DominikTobureto/awesome-grok-build · 37 tokens

add-llm-evals

Use this when adding evaluation to an LLM/agent app - measuring output quality (correctness, faithfulness, relevance, safety) rather than just watching traces. Trigger on "add evals", "test my prompt", "is my RAG accurate", "catch regressions", "score outputs", or setting up an eval suite in CI. Covers offline (CI)…

ContextJet-ai/awesome-llm-observability · 95 tokens

build-eval-dataset

Use this to build a good evaluation dataset for an LLM app, the part everyone underestimates. Trigger on "make an eval set", "what should I test my LLM on", "I don't have test data for my prompt", "build a golden dataset", or before setting up evals. A great eval set beats a great metric; garbage-in means your evals…

ContextJet-ai/awesome-llm-observability · 87 tokens

set-up-ab-testing

Use this to test an LLM change (new prompt, new model, new retrieval) on real traffic before rolling it out to everyone. Trigger on "A/B test my prompt", "roll out a new model safely", "compare two prompts in production", "canary this change", "does this actually improve things for real users". Measure impact on real…

ContextJet-ai/awesome-llm-observability · 86 tokens