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.
git clone --depth 1 https://github.com/seabbs/skillsWrote 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/plugins/seabbs/skills/lang-julia)<a href="https://agentmods.dev/plugins/seabbs/skills/lang-julia"><img src="https://agentmods.dev/badge/plugins/seabbs/skills/lang-julia/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/plugins/seabbs/skills/lang-julia"><img src="https://agentmods.dev/badge/plugins/seabbs/skills/lang-julia.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lang-julia 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
{
"name": "lang-julia",
"version": "1.0.0",
"description": "Julia package development following SciML standards"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 29 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 6 lines scan A d8c1e5bcf91c
lang-julia is a plugin published in the GitHub repository seabbs/skills (6 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
nvidia-cuopt-skills
Agent skills for NVIDIA cuOpt: routing (VRP, TSP, PDP), LP/MILP/QP, installation (Python/C/developer), and REST server. Use when building or solving optimization with cuOpt.
writing-lean-proofs
Structured Lean 4 proof writing and library design following Mathlib conventions.
lean4
Archon's modified Lean 4 plugin (draft, formalize, autoformalize, prove, autoprove, checkpoint, review, refactor, golf, learn, doctor) — forked from cameronfreer/lean4-skills.
powergridmodel
power-grid-model Python skill - high-performance steady-state distribution power system analysis: power flow, state estimation, and IEC 60909 short-circuit calculations with 22 component types and batch/parallel computation.
write-lean-code
Lean 4 and Mathlib conventions for code, proofs, naming, documentation and compile-time tests that mirror the public library API.
stata-c-plugins
Develop high-performance C/C++ plugins for Stata — SDK setup, .ado wrappers, cross-platform compilation, performance optimization, and Python/R package translation.