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 avsm/ocaml-claude-marketplace --skill doc-stylegit clone --depth 1 https://github.com/avsm/ocaml-claude-marketplaceWrote 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/avsm/ocaml-claude-marketplace/doc-style)<a href="https://agentmods.dev/skills/avsm/ocaml-claude-marketplace/doc-style"><img src="https://agentmods.dev/badge/skills/avsm/ocaml-claude-marketplace/doc-style/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/avsm/ocaml-claude-marketplace/doc-style"><img src="https://agentmods.dev/badge/skills/avsm/ocaml-claude-marketplace/doc-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.02130 |
| Opus 5.5 | $0.00038 | $0.00852 |
| Sonnet 5.5 | $0.00019 | $0.00426 |
| Haiku 4.5 | $0.00009 | $0.00213 |
Grade A, and why
doc-style 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OCaml Comment and Documentation Style
Write ocamldoc the way a POSIX manual page is written. State what a thing is and what it does, in full sentences, and stop.
Implementations carry no comments at all unless the code cannot speak for itself.
This skill covers what to write. For odoc reference syntax, cross-package
links and build warnings, see the ocaml-docs skill.
The Six Rules
- Full sentences. Every doc comment is one or more complete sentences, each ending in a full stop. No fragments, no bullet-point shorthand, no trailing "...".
- Manpage voice. Terse, declarative, present tense, third person. No "we", no "you", no "this function", no enthusiasm.
- No extraneous detail. Document what a caller must know to call it. History, rationale, benchmarks, future plans and implementation trivia do not appear.
- No connectives. No colons and no em dashes joining clauses. Split into separate sentences instead. Semicolons only inside a genuine list.
- User-facing, not internal. Describe observable behaviour. Mention an internal only when the caller can observe it, such as time complexity, allocation behaviour, evaluation order or thread safety.
[f x y] is .... A function's documentation opens with the function applied to its arguments in brackets, followed byis.
Function Documentation
The doc comment follows the val declaration. Name the arguments in the
bracketed application and refer to them with [x] thereafter.
val length : t -> int
(** [length t] is the number of elements in [t]. *)
val find : string -> t -> element option
(** [find name t] is the element of [t] called [name], or [None] if [t] has
no such element. *)
val is_bot : t -> bool
(** [is_bot u] is [true] if [u] is a bot user. *)
Use is whenever the function has a meaningful result. Reserve an active verb
for functions that exist for their effect.
val flush : out_channel -> unit
(** [flush oc] writes the buffered bytes of [oc] to its underlying file. *)
val set : t -> key:string -> value:string -> unit
(** [set t ~key ~value] binds [key] to [value] in [t]. Any previous binding of
[key] is dropped. *)
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 · 229 lines · 94 tokens per session scan A f044767e6254
doc-style is a skill published in the GitHub repository avsm/ocaml-claude-marketplace (37 stars, last pushed 1mo ago), licensed ISC. It adds 94 tokens to every session and 2,130 once invoked, about $0.0004 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-09-04.
Other skills, from other repositories
erlang-otp-behaviors
Use when oTP behaviors including genserver for stateful processes, genstatem for state machines, supervisors for fault tolerance, genevent for event handling, and building robust, production-ready Erlang applications with proven patterns.
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
axiom-concurrency
Use when writing ANY async code, actors, or threads in an Apple-platform app, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.
haskell-pro
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
splitting-oversized-modules
Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a human has agreed to…
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.