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/clima/ensemblekalmanprocesses.jl/docstringsnpx skills add CliMA/EnsembleKalmanProcesses.jl --skill docstringsgit clone --depth 1 https://github.com/CliMA/EnsembleKalmanProcesses.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.00167 | $0.05297 |
| Opus 5 | $0.00084 | $0.02648 |
| Sonnet 5 | $0.00033 | $0.01059 |
| Haiku 4.5 | $0.00017 | $0.00530 |
Grade A, and why
docstrings 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docstrings
Add or normalise Julia docstrings on public symbols (exported types, functions,
and constants) across the package source. The goal is complete, consistent API
documentation that renders correctly under Documenter.jl and follows whichever
docstring convention is already established in the package — typically
DocStringExtensions macros such as $(TYPEDEF), $(TYPEDFIELDS), and
$(TYPEDSIGNATURES). Completing this skill makes the package's public API fully
self-documenting and satisfies any checkdocs requirement in the docs build.
Workflow
Step 1 — Detect the existing convention
Use an Explore subagent to read 2–3 symbols that already have complete docstrings to calibrate style. This avoids consuming the main context window with large file reads. Ask the Explore agent to return the verbatim docstring text for each symbol.
Identify:
- Whether DocStringExtensions macros are used, and which ones (
$(TYPEDEF),$(TYPEDFIELDS),$(TYPEDSIGNATURES),$(METHODLIST)). - How prose is structured relative to macro-generated content (e.g. does prose
come before or after
$(TYPEDFIELDS)?). - What field documentation pattern is preferred: inline string literals above each struct field vs. a separate prose block.
- Which format is used for struct docstrings: the old format (an indented
type-name header on the first line, no
$(TYPEDEF), manual# Constructorsection), or the new format (prose only,$(TYPEDEF)for the signature,$(METHODLIST)for constructors). Normalise old-format structs to new-format during Step 3.
This detected baseline becomes the style target for every new or normalised docstring. Do not impose a different convention — match what is already there.
Step 2 — Enumerate candidates
Discover the package name from Project.toml (the name = field). Then run:
grep -nE '^(function |struct |abstract type |mutable struct |const )' src/**/*.jl
Cross-file exports: exported names may be declared in a central module file
(e.g. src/PackageName.jl) while the definition lives in a different file.
Read the module file for all export statements so you catch every public symbol
regardless of where it is defined.
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.
- 3d ago First seen · 537 lines · 167 tokens per session scan A 2d71dc0626a7
docstrings is a skill published in the GitHub repository CliMA/EnsembleKalmanProcesses.jl (118 stars, last pushed 5d ago), licensed Apache-2.0. It adds 167 tokens to every session and 5,297 once invoked, about $0.0008 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-30.
Other skills, from other repositories
bnlearn
Use this skill when working with bnlearn, a Python library for Bayesian networks, probabilistic graphical models, causal discovery, parameter learning, structure learning, inference, sampling, and directed acyclic graphs (DAG).
wxjava-module-selector
根据微信公众号、小程序、微信支付、企业微信、开放平台、视频号或微信小店、腾讯企点和微信智能对话等业务场景，为用户选择合适的 WxJava Maven 模块、BOM 和示例入口。适用于用户询问“该用哪个模块”、依赖坐标、产品边界或单/多账号 Starter 选择时。.
cpp-pro
Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
rust-pro
Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
ax-python-agent
Use when writing Python code with axllm for agents, child delegation, tools, MCP, citations, persistent playbook learning, stage instructions, runtime state, final typed responses, and direct-respond executor skipping.