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 fmind/dotfiles --skill cli-contractsgit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/fmind/dotfiles/cli-contracts)<a href="https://agentmods.dev/skills/fmind/dotfiles/cli-contracts"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/cli-contracts/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/fmind/dotfiles/cli-contracts"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/cli-contracts.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.00034 | $0.00594 |
| Opus 5.5 | $0.00014 | $0.00238 |
| Sonnet 5.5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
cli-contracts 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineer CLI Contracts
Define a command-line interface as a stable human and machine contract before implementing it. Pair with go-stack or python-stack for language-specific code and systematic-debugging for unknown failures.
Contract
- Name the jobs: Give each command one purpose, a predictable noun/verb hierarchy, and aliases only when they cannot trigger a different class of action.
- Specify inputs: Define positional arguments, flags, environment variables, config precedence, defaults, validation, mutual exclusions, and behavior without a TTY.
- Separate streams: Send requested data to stdout and diagnostics or progress to stderr. Keep
--jsonmachine-readable, schema-stable, and free of decoration. - Define outcomes: Map success, usage errors, authentication failures, remote failures, partial results, and cancellation to documented exit codes. Never convert an error into an empty success.
- Make help executable: Ensure root and subcommand help, examples, deprecations, and shell completions are generated from the same command definition.
- Protect sensitive context: Render safe command and argument context for actionable errors, but never include collected values, tokens, provider response bodies, or unredacted stderr.
- Handle process behavior: Respect signals, cancellation, timeouts, piping, broken pipes, and cleanup. Destructive commands need a confirmation mechanism or explicit non-interactive opt-in, while agent execution still requires separate target-scoped user authority; a
--yesflag is never authority. - Preserve compatibility deliberately: Treat command names, flags, JSON fields, exit codes, and stdout text consumed by scripts as public API. Prefer deprecation and migration guidance over silent changes.
Verification
- Write contract tests for help, parsing, validation, streams, exit codes, JSON schema, cancellation, and representative success and failure paths.
- Exercise the installed binary from a clean shell, including piped and non-TTY use; do not rely only on direct function tests.
- Run the focused tests, completion generation, documentation checks, and the repository's full gate.
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 · 36 lines · 34 tokens per session scan A 4de8c8762459
cli-contracts is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 594 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
full-review
Full review: read every repo area, apply verified fixes, and prove all checks pass.
duckdb
Query and export CSV, Parquet, JSON, or SQLite data with DuckDB.
observability
Instrument Python services and agents: structlog logs, OpenTelemetry traces and metrics.
resolve-conflicts
Resolve Git merge or rebase conflicts by both sides' intent; verify the result.
skill-security-review
Review third-party skills and agent extensions for supply-chain risk.
sops-secrets
Encrypt, rotate, and inject Git secrets with sops and age.