Borrowing it
Nothing to install: this file belongs to belingud/yaicli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/belingud/yaicli/master/CLAUDE.mdgit clone --depth 1 https://github.com/belingud/yaicliWrote 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/belingud/yaicli/claude-md)<a href="https://agentmods.dev/instructions/belingud/yaicli/claude-md"><img src="https://agentmods.dev/badge/instructions/belingud/yaicli/claude-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.1 | $0.00791 | $0.00791 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
yaicli CLAUDE.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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance when working with code in this repository.
Project Overview
YAICLI is a CLI tool for interacting with LLMs from the terminal. It supports 30+ providers (OpenAI, Anthropic, Gemini, Ollama, etc.), multiple interaction modes (chat, shell command execution, quick query), function calling, and MCP integration.
Common Commands
# Install dependencies (all extras for development)
uv sync --all-groups --all-extras
# Run tests
uv run pytest # all tests
uv run pytest tests/test_cli.py # single file
uv run pytest -k "test_name" # single test by name
uv run pytest --cov=yaicli # with coverage
# Multi-version testing
tox # all Python versions (3.10-3.13)
tox -e py312 # specific version
tox -e lint # lint only
# Linting and formatting
just format # format with ruff + isort
ruff check yaicli tests # check only
ruff check --fix yaicli tests # check and fix
# Build
uv build
# Version bump (uses bump2version)
uv run bump2version patch|minor|major
Architecture
Core Flow
entry.py (Typer app) → cli.py (CLI orchestrator) → llms/client.py (LLMClient)
→ llms/provider.py (ProviderFactory → Provider)
Key Modules
yaicli/cli.py: Main orchestrator handling chat, exec, and temp modes. Manages roles, sessions, keybindings, and history.yaicli/llms/client.py:LLMClientcoordinates provider calls, tool execution (recursive with depth limit), and streaming.yaicli/llms/provider.py:ProviderABC +ProviderFactory. Each provider inproviders/extends this.yaicli/config.py: Layered config (env varsYAI_*> config file~/.config/yaicli/config.ini> defaults).yaicli/tools/function.py: Function calling schema generation and execution.yaicli/tools/mcp.py: MCP protocol integration (lazy-loaded).yaicli/printer.py: Rich text rendering for streaming responses.
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.
- 6d ago First seen · 81 lines · 791 tokens per session scan A 58419a3a8a66
yaicli CLAUDE.md is an instructions file published in the GitHub repository belingud/yaicli (19 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 791 tokens to every session, about $0.0040 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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).
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.
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.