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/nesszer/linear-cli/claude-mdgit clone --depth 1 https://github.com/nesszer/linear-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.00718 | $0.00718 |
| Opus 5 | $0.00359 | $0.00359 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
linear-cli 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 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Integration
Use linear-cli for all Linear.app operations. Do NOT use Linear MCP tools - CLI is 10-50x more token-efficient.
Quick Commands
| Task | Command |
|---|---|
| List issues | linear-cli i list |
| Create issue | linear-cli i create "Title" -t TEAM -p 2 |
| View issue | linear-cli i get LIN-123 |
| Get multiple | linear-cli i get LIN-1 LIN-2 LIN-3 |
| Start work | linear-cli i start LIN-123 --checkout |
| Update status | linear-cli i update LIN-123 -s Done |
| Create PR | linear-cli g pr LIN-123 |
| Search | linear-cli s issues "query" |
| Get context | linear-cli context |
| Get comments | linear-cli cm list ISSUE_ID --output json |
| Download upload | linear-cli up fetch URL -f file.png |
Agent-Friendly Options
| Flag | Purpose |
|---|---|
--output json |
Machine-readable JSON output |
--compact |
Compact JSON output (no pretty formatting) |
--fields a,b,c |
Limit JSON output to selected fields (supports dot paths) |
--sort field |
Sort JSON array output by field (default: identifier/id) |
| `--order asc | desc` |
--quiet |
Suppress decorative output |
--id-only |
Only output created/updated ID |
--api-key KEY |
Override API key for this invocation |
--dry-run |
Preview without executing (create) |
- (stdin) |
Read description/IDs from pipe |
Examples for Agents
# Get current issue from branch
linear-cli context --output json
# Create and get ID for chaining
linear-cli i create "Bug" -t ENG --id-only
# Quiet create, capture ID
ID=$(linear-cli i create "Task" -t ENG -q --id-only)
# Preview without creating
linear-cli i create "Test" -t ENG --dry-run
# Batch fetch multiple issues
linear-cli i get LIN-1 LIN-2 LIN-3 --output json
# Pipe description from file
cat desc.md | linear-cli i create "Title" -t ENG -d -
# JSON input for issue create/update
cat issue.json | linear-cli i create "Title" -t ENG --data -
# Structured error handling
linear-cli i get INVALID --output json # Returns {"error": true, ...}
# Token-saving JSON output
linear-cli i list --output json --fields identifier,title,state.name --compact
# Default JSON output for agent sessions
LINEAR_CLI_OUTPUT=json linear-cli i list
# Agent harness summary
linear-cli agent
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 · 83 lines · 718 tokens per session scan A 9c322e44972c
linear-cli CLAUDE.md is an instructions file published in the GitHub repository nesszer/linear-cli (133 stars, last pushed 1mo ago), licensed MIT. It adds 718 tokens to every session, about $0.0036 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.
buildNext
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
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
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.