agentmods.dev

linear-expand

linear-expand is a skill for Claude Code from toolwright-adk/toolwright-monorepo. It costs 65 tokens per session (904 once invoked), scanned A, original, MIT.

A planning skill for adding an epic and several related issues to an existing Linear project. It connects the work to milestones and applies suitable labels and structure.

In plain words
What is it for?
Use it to expand a Linear project with three or more connected pieces of work, such as a new feature area or implementation phase.
Why use it?
It avoids manually creating and wiring a group of related tasks into a project that already exists.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the linear-project-manager plugin — 3 skills, 2 commands, 2 agents shipped together

not rated 1repo 7mo ago A scan 65 tokens original MIT

Good fit Use it to expand a Linear project with three or more connected pieces of work, such as a new feature area or implementation phase.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/toolwright-adk/toolwright-monorepo/linear-expand
View source ↗ toolwright-adk/toolwright-monorepo
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.

Any agent
npx skills add toolwright-adk/toolwright-monorepo --skill linear-expand
Clone the repo
git clone --depth 1 https://github.com/toolwright-adk/toolwright-monorepo

Made for: Claude Code.

Or install linear-project-manager, the plugin that ships this one along with the rest of its 3 skills, 2 commands, 2 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for linear-expand

README.md
[![agentmods](https://agentmods.dev/badge/skills/toolwright-adk/toolwright-monorepo/linear-expand/github.svg)](https://agentmods.dev/skills/toolwright-adk/toolwright-monorepo/linear-expand)
Your own site
<a href="https://agentmods.dev/skills/toolwright-adk/toolwright-monorepo/linear-expand"><img src="https://agentmods.dev/badge/skills/toolwright-adk/toolwright-monorepo/linear-expand/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for linear-expand

Your own site · 80×15
<a href="https://agentmods.dev/skills/toolwright-adk/toolwright-monorepo/linear-expand"><img src="https://agentmods.dev/badge/skills/toolwright-adk/toolwright-monorepo/linear-expand.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 904 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00065 $0.00904
Opus 5.5 $0.00026 $0.00362
Sonnet 5.5 $0.00013 $0.00181
Haiku 4.5 $0.00006 $0.00090

Measured 1mo ago against content hash e8bc59a01290, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

linear-expand 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 1mo 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.

packages/linear-project-manager/skills/linear-expand/SKILL.md · 96 lines

How it starts

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

Expand a Linear Project

Add an epic with child issues to an existing project using add-epic — one call that gets parent/child structure, milestone wiring, and labels automatically.

When to Use This vs. Other Tools

  • 3+ related issues that form a logical group → use this skill (add-epic)
  • 1-2 standalone issues → just use mcp__linear__save_issue directly
  • New project from scratch → use /linear-bootstrap instead

Workflow

0. Verify prerequisites

Confirm mcp__linear-bootstrap__add-epic is available. If not, tell the user the linear-bootstrap MCP server is not running and suggest troubleshooting.

1. Find the target project

Use $ARGUMENTS or ask the user which project to expand. Use mcp__linear__list_projects if needed.

2. Understand current project structure

Gather in parallel:

  • mcp__linear__get_project — project overview
  • mcp__linear__list_milestones — existing milestones (to wire the new epic to one)
  • mcp__linear__list_issues — existing issues (to avoid duplicates and understand naming patterns)
  • mcp__linear-bootstrap__introspect-workspace — team labels and workflow states (for label reuse)

3. Design the epic

From the user's description, determine:

  • Epic title and description
  • Which milestone to attach to (pick the most appropriate existing one)
  • Child issues with titles, priorities, estimates, labels, and dependencies
  • Labels to apply (reuse existing team labels where possible)

Show the user a summary: "I'll add epic 'Payment Retry Logic' with 5 issues to milestone 'M3: Checkout Flow'. Sound right?"

4. Create with add-epic

Use mcp__linear-bootstrap__add-epic with:

  • project_id — from step 2
  • team_id — from the project's team
  • epic — the designed structure
  • milestone_id — from step 2
  • label_ids — map of label name → ID from introspection

Report what was created: epic ID, child issue count, milestone, labels applied.

5. Handle errors

If add-epic fails partially, report what was created vs. what failed. The successfully created items remain in Linear.

Read the full file on GitHub · 96 lines

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. 1mo ago First seen · 96 lines · 65 tokens per session scan A e8bc59a01290

Subscribe to this mod's changes

linear-expand is a skill published in the GitHub repository toolwright-adk/toolwright-monorepo (1 stars, last pushed 7mo ago), licensed MIT. It adds 65 tokens to every session and 904 once invoked, about $0.0003 per session on Opus 5.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-31.

Project management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens