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 skills add samtalki/AgentREPL.jl --skill julia-developgit 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-develop)<a href="https://agentmods.dev/skills/samtalki/agentrepl.jl/julia-develop"><img src="https://agentmods.dev/badge/skills/samtalki/agentrepl.jl/julia-develop/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.
<a href="https://agentmods.dev/skills/samtalki/agentrepl.jl/julia-develop"><img src="https://agentmods.dev/badge/skills/samtalki/agentrepl.jl/julia-develop.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00503 |
| Opus 5.5 | $0.00007 | $0.00201 |
| Sonnet 5.5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
julia-develop 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.
What it actually says
Julia Development Workflow
Set up a complete Julia development workflow with project activation, dependency installation, and Revise.jl hot-reloading.
Arguments
path- Path to the project directory (default: current directory ".")
Instructions
Execute these steps in sequence:
-
Activate the project:
activate(path="<path>") -
Install dependencies:
pkg(action="instantiate") -
Load the package (if it's a Julia package with
src/<PkgName>.jl):eval(code="using <PkgName>") -
Verify Revise.jl is available:
revise(action="status")If Revise is not available:
pkg(action="add", packages="Revise")Then reset to reload (Revise auto-loads on startup).
-
Report the setup to the user:
- Project path
- Installed dependencies
- Package loaded
- Revise.jl status
- Ready for iterative development
Development Cycle
Once set up, the iterative development cycle is:
- Edit source files — Claude edits
.jlfiles as needed - Hot-reload —
revise(action="revise")picks up changes - Test —
evalto run code, orpkg(action="test")for full test suite - Repeat — no session restart needed
For Package Development
When developing a local package alongside a project:
pkg(action="develop", packages="./path/to/MyPkg")
This puts the package in development mode. Combined with Revise, any edits to the package source are automatically picked up without restarting.
When done:
pkg(action="free", packages="MyPkg")
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.
- 1mo ago First seen · 80 lines · 17 tokens per session scan A e1fc07b5e2b4
julia-develop is a skill published in the GitHub repository samtalki/AgentREPL.jl (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 503 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-31.
Other skills, from other repositories
language-idioms-refiner
Facilitate a structured conversation to define language-specific idioms and patterns for a repository. Produces a language-idioms.md document consumed by multiple atoms to adapt pseudocode defaults to the project's language. Use when setting up a new project, switching languages, or when the user says 'setup…
leiloeiro-edital-ranbot-ai
Analise e auditoria de editais de leilao judicial e extrajudicial. Riscos ocultos, clausulas perigosas, debitos, ocupante e classificacao da oportunidade.
arkts-syntax-assistant
ArkTS syntax, migration, and optimization guide for HarmonyOS/OpenHarmony development. Triggers on: .ets files, ArkTS keywords, HarmonyOS/OpenHarmony context, @ohos packages. Help with syntax reference, TypeScript migration, performance optimization, compile errors, state management, component development, and…
matlab
Builds, reviews, migrates, and plans MATLAB or GNU Octave numerical workflows. Use for arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
pennylane
Builds and differentiates PennyLane quantum circuits, hybrid PyTorch or JAX models, molecular VQE and QAOA workflows. Use for variational quantum algorithms, quantum machine learning, simulator validation, and moving validated circuits to provider plugins. For hardware-specific compilation use qiskit or cirq; for…
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…