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/agents-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.00987 | $0.00987 |
| Opus 5 | $0.00494 | $0.00494 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
linear-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.
How it starts
The opening of the file, as written. The whole thing — 58 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.
Commands
linear-cli i list- List issueslinear-cli i list -t TEAM- List team's issueslinear-cli i create "Title" -t TEAM- Create issuelinear-cli i get LIN-123- View issue detailslinear-cli i get LIN-1 LIN-2 LIN-3- Batch fetch multiple issueslinear-cli i get LIN-123 --output json- View as JSONlinear-cli i update LIN-123 -s Done- Update statuslinear-cli i start LIN-123 --checkout- Start work (assign + branch)linear-cli g pr LIN-123- Create GitHub PRlinear-cli g pr LIN-123 --draft- Create draft PRlinear-cli s issues "query"- Search issueslinear-cli context- Get current issue from git branchlinear-cli update- Check for and install the latest CLI releaselinear-cli cm list ISSUE_ID --output json- Get comments as JSONlinear-cli up fetch URL -f file.png- Download attachments
Agent-Friendly Flags
--output json- Machine-readable 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- Sort order for JSON array output--quietor-q- Suppress decorative output--id-only- Output only created/updated ID--api-key KEY- Override API key for this invocation--dry-run- Preview without executing (create)-d -- Read description from stdin
Exit Codes
- 0 = Success
- 1 = General error
- 2 = Not found
- 3 = Auth error
- 4 = Rate limited
Notes
- Set
LINEAR_CLI_OUTPUT=jsonto default all output to JSON - Errors with
--output jsonreturn{"error": true, "message": "...", "code": N, "details": {...}, "retry_after": N} linear-cli i create/updateaccept--dataJSON input (use-for stdin)linear-cli agentprints agent-focused capabilities and exampleslinear-cli update --checkreports current vs latest release without installing- JSON samples live in
docs/json/ - Use
--helpon any command for full options
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 · 58 lines · 987 tokens per session scan A 84d9d466681c
linear-cli AGENTS.md is an instructions file published in the GitHub repository nesszer/linear-cli (133 stars, last pushed 1mo ago), licensed MIT. It adds 987 tokens to every session, about $0.0049 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.