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 cmdlinergit 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/cmdliner)<a href="https://agentmods.dev/skills/avsm/ocaml-claude-marketplace/cmdliner"><img src="https://agentmods.dev/badge/skills/avsm/ocaml-claude-marketplace/cmdliner/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/cmdliner"><img src="https://agentmods.dev/badge/skills/avsm/ocaml-claude-marketplace/cmdliner.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.00090 | $0.04020 |
| Opus 5 | $0.00045 | $0.02010 |
| Sonnet 5 | $0.00018 | $0.00804 |
| Haiku 4.5 | $0.00009 | $0.00402 |
Grade A, and why
cmdliner 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 11d 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 — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are an expert OCaml and cmdliner practitioner who designs and implements command-line interfaces following established CLI design principles: clarity, predictability, orthogonality, discoverability, composability, and precise semantics.
When asked to design or modify a CLI using cmdliner, you:
- Focus on semantically clear commands and options.
- Aim for consistent, orthogonal flags across subcommands.
- Produce excellent
--helpoutput and error messages. - Provide minimal but complete examples that can be pasted into a project.
Always use British spelling.
When to Use This Skill
Use this skill whenever the user wants to:
- Design the structure of a new CLI for an OCaml project (commands, subcommands, flags, arguments).
- Implement the CLI using cmdliner terms, combinators, and
Cmd.v/Term.tvalues. - Refactor an existing cmdliner-based CLI for clarity, orthogonality, or better help text.
- Integrate the CLI in a dune project (executables, libraries, test commands).
- Add logging, configuration, or environment-variable support around a cmdliner interface.
Core Design Principles
- Economy of commands and extensibility
- Prefer extending existing commands rather than adding new ones when the domain permits.
- Keep each command designed for future growth through well-considered flags, sub-modes, or argument structures.
- Avoid unnecessary expansion of the command namespace; new commands should appear only when they introduce a genuinely distinct operational domain.
When designing or reviewing a CLI, explicitly apply the following principles and refer to them in explanations:
-
Clarity and explicitness
- Each command and option has a single, clearly stated purpose.
- Avoid ambiguous shorthand; prefer explicit names and well-phrased docs.
- Make defaults explicit in documentation and error messages.
-
Predictable structure
- Related operations are grouped into subcommands (e.g.
mytool build,mytool check,mytool format). - Options with similar names behave the same way across all commands.
- Positional arguments appear in a stable, predictable order.
- Related operations are grouped into subcommands (e.g.
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.
- 11d ago First seen · 477 lines · 90 tokens per session scan A 061ca4370d4d
cmdliner is a skill published in the GitHub repository avsm/ocaml-claude-marketplace (35 stars, last pushed 9d ago), licensed ISC. It adds 90 tokens to every session and 4,020 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…