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/samtalki/agentrepl.jl/julia-sessionnpx skills add samtalki/AgentREPL.jl --skill julia-sessiongit clone --depth 1 https://github.com/samtalki/AgentREPL.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/samtalki/agentrepl.jl/julia-session)<a href="https://agentmods.dev/skills/samtalki/agentrepl.jl/julia-session"><img src="https://agentmods.dev/badge/skills/samtalki/agentrepl.jl/julia-session.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 | $0.00019 | $0.00456 |
| Opus 5 | $0.00010 | $0.00228 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
julia-session 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 4d 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
Julia Session Management
Manage multiple concurrent Julia REPL sessions. Each session has its own isolated worker process with separate state, packages, and project environment.
Arguments
action- One of:create,switch,list,destroyname- Session name (required for create/switch/destroy)
Instructions
Parse the user's arguments:
| User Input | Action | Name |
|---|---|---|
create analysis |
create | analysis |
switch testing |
switch | testing |
list |
list | (none) |
destroy old-session |
destroy | old-session |
Call session with the appropriate action and name parameters.
When to Create Separate Sessions
- Development + Testing: One session for development work, another for running tests
- Multiple Projects: One session per project when working across repos
- Benchmarking: Isolate benchmark runs from development state
- Experimentation: Try something risky without affecting your main session
Session Lifecycle
- Sessions start with no worker — workers spawn lazily on first
eval - Each session gets its own Malt.jl worker process
- Variables, packages, and project environment are fully isolated between sessions
- Revise.jl is auto-loaded on each worker if available
- The "default" session is auto-created if you use
evalwithout creating a session first
Notes
- Session names should be short, descriptive identifiers (e.g., "dev", "test", "analysis")
- Use
listto see all sessions with their worker status, project, and Revise availability - The
*marker in list output indicates the current session - Destroying a session kills its worker process immediately
- If you destroy the current session, another session becomes current automatically
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.
- 4d ago First seen · 54 lines · 19 tokens per session scan A fe89349a7909
julia-session is a skill published in the GitHub repository samtalki/AgentREPL.jl (6 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 456 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
bestie-features
Add BestieTemplate features (AGENTS.md, changelog, dependabot, pre-commit, lint workflow, testitem runner) to a Julia package with the bestie CLI — no Julia needed. Use when asked to add one of these files/setups to a package, or to see what BestieTemplate can add.
aatmf-t10-confidentiality-breach
AATMF T10 — Integrity & Confidentiality Breach. System prompt extraction, training-data extraction, model-weight leakage, private-key recovery.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
lazarus-group
Adversary-emulation profile for Lazarus Group (G0032, aka Hidden Cobra / Diamond Sleet / Labyrinth Chollima), a North Korean RGB-linked actor conducting espionage, destructive, and financially motivated operations.
sidewinder-rattlesnake
Adversary-emulation profile for SideWinder (G0121 / Rattlesnake / T-APT-04 / Razor Tiger), India's suspected state-sponsored cyber-espionage actor.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…