A connection between an agent and Linear, a tool for managing software issues and project tickets. It can find issues, read their details, change their workflow state, and add comments.

Use it when working from issue IDs such as ENG-123, checking assigned or open tickets, reporting progress, moving work through states, or posting a pull-request link.

It keeps ticket-driven coding work connected to the issue tracker. It also ensures state changes use the correct workflow option for the relevant team.

linear — Skill by initializ

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/initializ/forge/linear

Any agent

npx skills add initializ/forge --skill linear

Clone the repo

git clone --depth 1 https://github.com/initializ/forge

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 2,002 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5	$0.00022	$0.02002
Opus 5	$0.00011	$0.01001
Sonnet 5	$0.00004	$0.00400
Haiku 4.5	$0.00002	$0.00200

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

Security

Grade A, and why

linear scanned grade A with 1 finding 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 yesterday.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/common.sh, scripts/linear-add-comment.sh, scripts/linear-get-issue.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- curl

forge-skills/local/embedded/linear/SKILL.md · 216 lines

How it starts

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

Linear Skill

You can read, search, and update Linear issues, list workflow states, and post comments. Use this skill as the entry point for ticket-driven workflows — turn ENG-123 into a structured payload, transition state, comment on progress.

When to use this skill

The user references a Linear issue by identifier (ENG-123, OPS-7, etc.).
The user asks for "my tickets" / "open issues" / "what's assigned to me".
An automation needs to mark work started, post a PR link as a comment, or move a ticket through workflow states.

Issue identifier format

Linear identifiers look like <TEAM_KEY>-<NUMBER> — ENG-123, OPS-7. They are not GraphQL UUIDs. The Linear API accepts both forms on issue(id:), so always pass the human identifier the user gave you. Never invent or normalise identifiers — use them verbatim.

State transition pattern (hard rule)

You MUST call linear_get_workflow_states first and use the resolved id when calling linear_update_issue_state. State IDs are per-team UUIDs; state names like "Todo" or "In Progress" are not portable across teams and cannot be passed to linear_update_issue_state directly.

Workflow:

linear_get_issue to find the issue's team.id.
linear_get_workflow_states with that team_id to enumerate the team's states.
Pick the state by matching its name (case-insensitive) or type (unstarted, started, completed, canceled, triage, backlog).
linear_update_issue_state with the issue identifier and the resolved state_id.

Commenting etiquette

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

yesterday First seen · 216 lines · 22 tokens per session scan A d57357527e48

Subscribe to this mod's changes

linear is a skill published in the GitHub repository initializ/forge (156 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 2,002 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Productivity Project Management Project management a2a a2a-protocol agent-cli ai-agents ai-agents-cli ai-workforce issue-tracking linear tickets workflow

Linear

Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.

wrsmith108/linear-claude-skill · 32 tokens

star-plan-decomposer

Break a research plan down into executable sub-plans with concrete, checkable steps — turning its method or milestones into actionable tasks. Reads the parent plan (written by star-plan-coach and living under metds/plans/), picks a decomposition axis (phase / component / evidence), confirms the unit list, then by…

wanghao9610/STAR · 202 tokens

star-plan-executor

Execute or implement a leaf research sub-plan: turn it into code and run light validation. Orients in the codebase using .env, turns the sub-plan from metds/plans/ into a concrete checked execution plan, implements it with surgical changes, keeps intermediate working files under a plan-specific tasks directory…

wanghao9610/STAR · 171 tokens

star-refs-reviewer

Literature review and related work: per-paper analysis notes plus a verified reference.bib. Builds an auditable base — 5–10 close papers read into notes, plus a classified reference.bib of ≥50 verified entries. No argument finds the method in metds/ and runs the full pass, resuming if metds/refs/ exists; a PLANNAME or…

wanghao9610/STAR · 226 tokens

star-code-release

Open-source or publish the project: gather scattered code, polish it, compile README.md. Consolidates into ${CODENAME}/, sweeping tasks/, wkdrs/ and the root, promoting only code passing a three-part evidence test (the README cites it, an executed leaf needs it, or it reproduces a results.md number), placed by…

wanghao9610/STAR · 195 tokens

star-code-reviewer

Review code quality, docstrings, and whether a plan's code matches what it promised. No argument reviews all of ${CODENAME}/; a PLANNAME (slug / prefix / filename) reviews that plan's files plus conformance (§3 tasks, §4 deliverables, §5 done-criterion); a path reviews that path; diff or a git range reviews changed…

wanghao9610/STAR · 198 tokens

linear