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 instructions/camil-h/cli-agent-lint/agents-mdgit clone --depth 1 https://github.com/Camil-H/cli-agent-lintWrote 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/instructions/camil-h/cli-agent-lint/agents-md)<a href="https://agentmods.dev/instructions/camil-h/cli-agent-lint/agents-md"><img src="https://agentmods.dev/badge/instructions/camil-h/cli-agent-lint/agents-md.svg" alt="Measured on agentmods" 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 | $0.00466 | $0.00466 |
| Opus 5 | $0.00233 | $0.00233 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
cli-agent-lint AGENTS.md 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 4d 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.
What it actually says
cli-agent-lint — Agent Skill File
What this tool does
cli-agent-lint audits CLI tools for AI agent-readiness. It checks across five categories: flow safety, token efficiency, self-describing, automation safety, and predictability.
Usage
# Audit a CLI tool
cli-agent-lint check <target-cli>
# JSON output (machine-readable)
cli-agent-lint check <target-cli> --output json
# Passive checks only (no subprocess execution)
cli-agent-lint check <target-cli> --no-probe
# List all checks
cli-agent-lint checks
# Describe a specific check
cli-agent-lint checks <check-id>
Exit codes
- 0: all checks passed
- 1: one or more fail-severity checks did not pass
- 2: cli-agent-lint itself errored
Key flags
--output json— structured JSON report to stdout--no-color— disable ANSI colors--quiet— suppress diagnostics, only essential output--no-probe— passive checks only, no subprocess execution--severity <level>— minimum severity: info, warn, fail--category <name>— filter by check category--skip <id>— skip specific checks (repeatable)--timeout <duration>— probe timeout (default 5s)
Security
Active checks (default) execute the target CLI as a subprocess. Use --no-probe when auditing untrusted CLIs to restrict to passive help-text analysis only. Sensitive environment variables (tokens, secrets, API keys) are stripped before execution, but the target can still make network requests and read local files.
Interpreting results
The JSON report contains a score object with percentage and grade (A-F). Each check in the checks array has id, status (pass/fail/warn/skip), severity, and recommendation.
Conventions
- Errors and diagnostics go to stderr
- Data output goes to stdout
- No interactive prompts — all input via flags/args
- Respects NO_COLOR env var
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.
- 4d ago First seen · 57 lines · 466 tokens per session scan A bd058c365c99
cli-agent-lint AGENTS.md is an instructions file published in the GitHub repository Camil-H/cli-agent-lint (56 stars, last pushed 3mo ago), licensed MIT. It adds 466 tokens to every session, about $0.0023 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.