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 commands/toolwright-adk/toolwright-monorepo/lineargit clone --depth 1 https://github.com/toolwright-adk/toolwright-monorepoWhat 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.00035 | $0.00385 |
| Opus 5 | $0.00017 | $0.00192 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
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.
What it actually says
Linear Project Manager
Route the user's request to the appropriate workflow.
Pre-flight
Before routing, do a quick availability check: attempt mcp__linear-bootstrap__list-teams and mcp__linear__list_teams. If either fails, warn the user which MCP is unavailable and what functionality is limited. Suggest /linear-check for full diagnostics. Continue with whatever is available.
Routing
Based on $ARGUMENTS or the user's intent:
| Intent | Action |
|---|---|
| Create a new project, plan, or bootstrap | Invoke the linear-bootstrap skill with the description |
| Check project status, health, progress | Invoke the linear-status skill with the project name |
| Add an epic or batch of issues to a project | Invoke the linear-expand skill with the details |
| Single issue operations (create, update, triage) | Handle directly using official Linear MCP tools (save_issue, list_issues, etc.) |
| Check MCP health or diagnose setup | Invoke /linear-check |
| Unclear | Ask the user what they want to do with Linear |
Examples
/linear create a project for auth migration→ routes to/linear-bootstrap/linear status Checkout Redesign→ routes to/linear-status/linear add retry handling to the payments project→ routes to/linear-expand/linear assign ENG-456 to Sarah→ useslinear-opsagent/linear check→ routes to/linear-check
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 · 37 lines · 35 tokens per session scan A 6ea41075fa58
linear is a command published in the GitHub repository toolwright-adk/toolwright-monorepo (1 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 385 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).