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 skills/bendrucker/claude/linearnpx skills add bendrucker/claude --skill lineargit clone --depth 1 https://github.com/bendrucker/claudeWhat 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.00041 | $0.01492 |
| Opus 5 | $0.00020 | $0.00746 |
| Sonnet 5 | $0.00008 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
linear 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear
Tools and workflows for managing issues, projects, and teams in Linear.
Environment
linearCLI: !linear --version 2>/dev/null || echo "not installed"
The connector and MCP paths need no CLI. The CLI-only operations (relations, bulk work) require linear; when it reads "not installed", stay on the connector. The version above tells you which CLI is installed. Confirm its exact subcommands and flags with linear <cmd> --help or the linear-cli:linear-cli skill rather than assuming them.
Arguments
$0 (optional verb) routes to an operation; pass the rest (issue id, title, filters) as its params. With no verb, infer the operation from the request.
create: create an issue. See Creating vs Updating and Issue Status in references/conventions.md.update: update an issue by id. See Creating vs Updating.list: query issues. See Querying Issues in references/conventions.md.view: fetch a single issue; include itsurlfor anything you may reference.comment: comment on an issue, using full URLs per Issue References in references/conventions.md.
Pick a tool path per Tool Selection.
Tool Selection
Three runtime paths reach Linear, in order of preference:
- Claude.ai connector (
mcp__claude_ai_Linear__save_issue,get_issue) is the primary path. One tool,save_issue, handles both create and update. It also takes relations (blocks,blockedBy,relatedTo,duplicateOf),parentId,project,milestone,cycle,estimate,dueDate, andlinksas params. That covers most structured single-issue work end to end. See Creating vs Updating. - Local or plugin MCP (
create_issue,update_issue,list_issues) exposes separate tools for create and update. Use it for simple single-issue operations when the connector is unavailable. linearCLI and raw GraphQL is the fallback for what the connector does not cover (complex queries, bulk operations) and for setting relations when the connector is unavailable. Defer to thelinear-cli:linear-cliskill for the CLI surface. See GraphQL API.
What ships with it
3 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.
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 · 120 lines · 41 tokens per session scan A 7636db15611b
linear is a skill published in the GitHub repository bendrucker/claude (16 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 1,492 once invoked, about $0.0002 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 skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.