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/toolwright-adk/toolwright-monorepo/linear-expandnpx skills add toolwright-adk/toolwright-monorepo --skill linear-expandgit clone --depth 1 https://github.com/toolwright-adk/toolwright-monorepoWrote 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.
[](https://agentmods.dev/skills/toolwright-adk/toolwright-monorepo/linear-expand)<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="Measured on agentmods" height="20"></a>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.1 | $0.00065 | $0.00904 |
| Opus 5 | $0.00032 | $0.00452 |
| Sonnet 5 | $0.00013 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00090 |
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 5d 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 — 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_issuedirectly - New project from scratch → use
/linear-bootstrapinstead
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 overviewmcp__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 2team_id— from the project's teamepic— the designed structuremilestone_id— from step 2label_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.
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.
- 5d ago First seen · 96 lines · 65 tokens per session scan A e8bc59a01290
linear-expand is a skill published in the GitHub repository toolwright-adk/toolwright-monorepo (1 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 904 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…