linear-list

A command-line tool for listing Linear issues and retrieving their details. Linear is a work-tracking app used to organize tasks, bugs, and other pieces of work.

In plain words
What is it for?
Finding issues by team, status, or assignee; fetching one or several issues; sorting results; and producing compact JSON for scripts or coding agents.
Why use it?
It provides a quick way to check issues from a terminal and return only the fields or results you need.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/nesszer/linear-cli/linear-list
Any agent
npx skills add nesszer/linear-cli --skill linear-list
Clone the repo
git clone --depth 1 https://github.com/nesszer/linear-cli

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 229 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00022 $0.00229
Opus 5 $0.00011 $0.00114
Sonnet 5 $0.00004 $0.00046
Haiku 4.5 $0.00002 $0.00023

Measured 2d ago against content hash cf91ff211357, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

linear-list 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.

skills/linear-list/SKILL.md · 36 lines

What it actually says

List/Get Issues

# List issues
linear-cli i list                    # All
linear-cli i list -t ENG             # By team
linear-cli i list -s "In Progress"   # By status
linear-cli i list --assignee me      # My issues

# Get issue(s)
linear-cli i get LIN-123
linear-cli i get LIN-1 LIN-2 LIN-3   # Multiple

# Agent-optimized
linear-cli i list --output json --compact --fields identifier,title,state.name

Flags

Flag Purpose
--output json JSON output
--compact No formatting
--fields a,b Select fields
--sort field Sort results

Exit Codes

0=Success, 1=Error, 2=Not found, 3=Auth error

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. 2d ago First seen · 36 lines · 22 tokens per session scan A cf91ff211357

Subscribe to this mod's changes

linear-list is a skill published in the GitHub repository nesszer/linear-cli (133 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 229 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens