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-developnpx skills add samtalki/AgentREPL.jl --skill julia-developgit clone --depth 1 https://github.com/samtalki/AgentREPL.jlWhat 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.00017 | $0.00503 |
| Opus 5 | $0.00009 | $0.00251 |
| Sonnet 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 2d 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.
- 2d 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 (6 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 503 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.
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
agentic-supply-chain-detection
Detect agentic supply-chain risks: compromised dependencies, malicious plugins/tools/models, and untrusted update sources.
skill-vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
ondb
A logical analysis and reasoning tool for AI. Use when decomposing documents into structured knowledge, querying entities and relations, validating consistency, or indexing files. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", "analyze this document", entity CRUD, or cross-skill…
finding-protocol
Operational-tier finding template — minimal fields for sub-agent decision support. Heavyweight deliverable promotion lives in skills/decepticon/final-report.