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/yogin16/better-cli/agents-mdgit clone --depth 1 https://github.com/yogin16/better-cliWhat 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.00361 | $0.00361 |
| Opus 5 | $0.00180 | $0.00180 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
better-cli 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 2d 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 Development Guidelines
When building or improving any CLI tool in this project, follow these principles:
Output Design
- stdout for data only, stderr for everything else (errors, warnings, progress)
- Support
--jsonwith a consistent envelope:{"status": "ok|error", "data": {...}} - Output must guide the next action — success shows "Next steps", failure shows "Fix"
- No ANSI escape codes when stdout is not a TTY; respect
NO_COLORenv var
Error Handling
- Exit 0 on success, semantic non-zero codes on failure (2=usage, 3=not found, 4=permission, 75=transient)
- Errors include: what went wrong, context, fix command, docs link
- Structured errors in JSON mode:
{"code": "AUTH_EXPIRED", "message": "...", "fix": "...", "transient": false}
Interactivity
- Every interactive prompt must have a flag equivalent (
--yes,--force,--name=value) - Never hang waiting for input when stdin is not a TTY
- Progress bars and spinners go to stderr only
Flags and Arguments
- Prefer flags over positional arguments for clarity
- Configuration precedence: flags > env vars > project config > user config > defaults
- Never accept secrets via flags (use env vars or
--password-file)
Composability
- Support
--fieldsto limit output columns - Support
--quietfor minimal output (IDs only) - Support
--dry-runfor mutating commands - Create commands output the created resource identifier
For the full guide, see the better-cli skill: SKILL.md
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.
- 2d ago First seen · 33 lines · 361 tokens per session scan A 2c4a854056f8
better-cli AGENTS.md is an instructions file published in the GitHub repository yogin16/better-cli (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 361 tokens to every session, about $0.0018 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
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.
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).
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.
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).
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.
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.