Caliber is a tool that generates and continuously updates AI context and configuration files for software repositories, including CLAUDE.md, AGENTS.md, and platform-specific rules. Development teams use it to keep coding agents aligned with the current codebase across tools such as Claude Code, Cursor, Codex, OpenCode, and GitHub Copilot. Its catalogue entries include skills, hooks, rules, instructions, and settings for configuring that workflow.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/caliber-ai-org/ai-setupnpx agentmods add skills/caliber-ai-org/ai-setup/adding-a-commandWrote 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/caliber-ai-org/ai-setup/adding-a-command)<a href="https://agentmods.dev/skills/caliber-ai-org/ai-setup/adding-a-command"><img src="https://agentmods.dev/badge/skills/caliber-ai-org/ai-setup/adding-a-command/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/caliber-ai-org/ai-setup/adding-a-command"><img src="https://agentmods.dev/badge/skills/caliber-ai-org/ai-setup/adding-a-command.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.00076 | $0.01851 |
| Opus 5.5 | $0.00030 | $0.00740 |
| Sonnet 5.5 | $0.00015 | $0.00370 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade A, and why
adding-a-command 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a Command
Critical
- Export pattern: Command must export a named async function:
export async function myCommand(options?: OptionType). Never use default exports. - Registration in cli.ts: Every command must be imported and registered with
.command()chain insrc/cli.ts, wrapped withtracked()for telemetry. - Error signaling: Use
throw new Error('__exit__')to exit gracefully without printing the error message. Use chalk for user-facing messages. - Options typing: Commands receiving options must define a TypeScript interface for those options. Pass options as a destructured object parameter.
Instructions
-
Create the command file at
src/commands/{commandName}.tswith named async export.- Signature:
export async function {commandName}Command(options?: { optionName?: optionType }) { ... } - Import only what you need (avoid kitchen-sink imports).
- Return void (handle all output via console.log or chalk).
- Verify the file follows the naming convention: camelCase function + "Command" suffix.
- Signature:
-
Handle errors consistently: Wrap error-prone operations in try/catch. Distinguish between user errors and system errors:
- User error (bad input):
console.error(chalk.red('message')); throw new Error('__exit__'); - System error (missing dependency):
throw new Error('Detailed error message');— this will print and exit with code 1. - Parse-like errors: Use ora spinner with
.fail()before throwing. - This step prevents double error printing in bin.ts.
- User error (bad input):
-
Import and register in src/cli.ts in the correct location:
- Add import at the top:
import { {commandName}Command } from './commands/{commandName}.js'; - Register the command in the appropriate section (main commands, or nested under a group like
sources). - For main commands:
.command('{kebab-name}').description('...').option(...).action(tracked('{kebab-name}', {commandName}Command)) - For subcommands (like
sources add):sources.command('add').description(...).action(tracked('sources:add', sourcesAddCommand)) - Key: Wrap handler with
tracked('{command-name}', handler)for automatic telemetry. - Verify the command name in tracked() uses kebab-case for main commands and colon-separated for subcommands.
- Add import at the top:
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 · 181 lines · 76 tokens per session scan A 73e93413cd36
adding-a-command is a skill published in the GitHub repository caliber-ai-org/ai-setup (1,307 stars, last pushed 23d ago), licensed MIT. It adds 76 tokens to every session and 1,851 once invoked, about $0.0003 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-30.
Other skills, from other repositories
implement-parse-list
Implement the parseList string utility.
typescript-patterns
Modern TypeScript best practices — strict types, utility types, generics, discriminated unions, and build tooling for production codebases.
effect
Work with Effect v4 / effect-smol TypeScript code in this repo.
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
bun-development
Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by oven-sh/bun.
bun-runtime
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.