cli: Instructions file for Claude Code

CLAUDE.md

cli CLAUDE.md is an instructions file for Claude Code from nylas/cli. It costs 1,451 tokens per session, scanned D, original, MIT.

A set of instructions for an AI coding assistant working on the Nylas CLI, a command-line tool for Nylas. It explains how the assistant should think, read code, and make changes.

In plain words
What is it for?
Use it when developing or reviewing the Nylas CLI. It guides planning, checking assumptions, following existing conventions, and verifying results.
Why use it?
It helps prevent unnecessary edits, guesses, hidden conflicts, and unverified work. It keeps changes small and consistent with the project.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is nylas/cli's own configuration. It tells Claude Code how to work on cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nylas/cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nylas/cli/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/nylas/cli

Made for: Claude Code.

Wrote 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.

agentmods badge for cli CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nylas/cli/claude-md/github.svg)](https://agentmods.dev/instructions/nylas/cli/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/nylas/cli/claude-md"><img src="https://agentmods.dev/badge/instructions/nylas/cli/claude-md/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.

agentmods 80×15 button for cli CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/nylas/cli/claude-md"><img src="https://agentmods.dev/badge/instructions/nylas/cli/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,451 This file is loaded in full into every session.
When invoked 1,451 The same file — it is already loaded in full.
Security scan D 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01451 $0.01451
Opus 5.5 $0.00580 $0.00580
Sonnet 5.5 $0.00290 $0.00290
Haiku 4.5 $0.00145 $0.00145

Measured 1mo ago against content hash 414aea4b4b72, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade D, and why

cli CLAUDE.md scanned grade D with 2 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Go build cache corruption: `sudo rm -rf ~/.cache/go-build ~/go/pkg/mod && go clean -cache`

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Go build cache corruption: `sudo rm -rf ~/.cache/go-build ~/go/pkg/mod && go clean -cache`
CLAUDE.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Nylas CLI — AI Assistant Rules

Every line traces to a real mistake. If Claude does it correctly without the instruction, delete it.


Working Principles

  1. Think Before Coding — State assumptions explicitly. If uncertain, ask. Push back when a simpler approach exists. Stop when confused — name what's unclear.
  2. Goal-Driven Execution — Define success criteria before starting. Loop until verified. Don't follow steps blindly — iterate toward success.
  3. Simplicity First — Minimum code that solves the problem. No speculative features. No abstractions for single-use code.
  4. Surgical Changes — Touch only what you must. Clean up only your own mess. Don't "improve" adjacent code or refactor what isn't broken.
  5. Read Before You Write — Before adding code, read exports, callers, shared utilities. "Looks orthogonal" is dangerous — this is the root cause of most LEARNINGS below. If unsure why code is structured that way, ask.
  6. Match Conventions — Conformance > taste. If you disagree with a convention, surface it — don't fork silently.
  7. Surface Conflicts, Don't Blend — If two patterns contradict, pick one (more recent / more tested). Explain why. Flag the other for cleanup.
  8. Tests Verify Intent — Tests encode WHY behavior matters, not just WHAT it does. A test that can't fail when business logic changes is wrong. Never modify existing tests to make implementation pass — fix the implementation instead.
  9. Checkpoint After Significant Steps — Summarize what was done, what's verified, what's left. If you lose track, stop and restate.
  10. Fail Loud — "Completed" is wrong if anything was skipped. "Tests pass" is wrong if any were skipped. Surface uncertainty, don't hide it.

Critical Rules

NEVER: commit secrets (.env, keys, tokens) · skip tests · skip security scans · skip linting · create files >600 lines

ALWAYS run before commits:

make ci-full   # Complete CI: quality + tests + cleanup
make ci        # Quick: fmt → vet → lint → test-unit → test-race → security → vuln → build

Read the full file on GitHub · 112 lines

Changes

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.

  1. 1mo ago First seen · 112 lines · 1,451 tokens per session scan D 414aea4b4b72

Subscribe to this mod's changes

cli CLAUDE.md is an instructions file published in the GitHub repository nylas/cli (76 stars, last pushed 12d ago), licensed MIT. It adds 1,451 tokens to every session, about $0.0058 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens