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-activategit 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-activate)<a href="https://agentmods.dev/skills/samtalki/agentrepl.jl/julia-activate"><img src="https://agentmods.dev/badge/skills/samtalki/agentrepl.jl/julia-activate/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-activate"><img src="https://agentmods.dev/badge/skills/samtalki/agentrepl.jl/julia-activate.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.00013 | $0.00286 |
| Opus 5.5 | $0.00005 | $0.00114 |
| Sonnet 5.5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
julia-activate 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 Activate
Activate a Julia project or environment for the current session.
Arguments
path- Path to project directory, "." for current directory, or named environment like "@v1.10"
Instructions
-
Parse the user's argument to determine the path:
- If no argument or ".", activate the current working directory
- If a path is given, use that path
- If starts with "@", it's a named environment
-
Call
activatewith the path -
After activation, offer to run
pkg(action="instantiate")to install dependencies if the project has a Project.toml
Examples
/julia:julia-activate .
/julia:julia-activate /path/to/MyProject
/julia:julia-activate @v1.10
Notes
- Activating a project changes where packages are installed/loaded from
- Use
pkg(action="instantiate")after activation to install dependencies - The activated environment persists across
resetcalls - Use
infoto see the currently active project
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 · 43 lines · 13 tokens per session scan A 387e7144fc79
julia-activate is a skill published in the GitHub repository samtalki/AgentREPL.jl (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 286 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
architecture-refiner
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a…
review
Perform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when…
skill-review
Deep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (conventions…
context-anchoring
Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles).…
ddd-refiner
Facilitate a structured conversation to define DDD guardrails for domain design within a repository. Produces a formal ddd-principles.md document that the domain-driven-design atom will use as its override. Use when setting up domain design principles, defining aggregate rules, or when the user says 'setup DDD'…
skill-align
Audit and fix all Lattice documentation, README, docs/, PROJECT.md, GitHub issue templates, and CLAUDE.md to ensure they are fully aligned with the current skill inventory. Documentation drift is the most common source of user confusion in Lattice — a skill exists in the codebase but not in the docs, or a renamed…