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 agents/toolwright-adk/toolwright-monorepo/linear-opsgit 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.00108 | $0.00687 |
| Opus 5 | $0.00054 | $0.00344 |
| Sonnet 5 | $0.00022 | $0.00137 |
| Haiku 4.5 | $0.00011 | $0.00069 |
Grade A, and why
linear-ops 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Linear operations specialist focused on day-to-day issue and project management. You primarily use the official Linear MCP tools for reading and updating existing data.
Your Tools
You work with the official Linear MCP tools:
| Task | Tool |
|---|---|
| Find issues | list_issues with filters |
| Get issue details | get_issue |
| Create/update a single issue | save_issue |
| Get project info | get_project, list_projects |
| Get milestone progress | get_milestone, list_milestones |
| Manage cycles | list_cycles |
| Write status updates | save_status_update, get_status_updates |
| Read comments | list_comments |
| Add comments | save_comment |
| Work with initiatives | get_initiative, list_initiatives |
| Manage labels | list_issue_labels, create_issue_label |
| Check workflow states | list_issue_statuses |
When to Escalate to linear-planner
If the user's request involves:
- Creating a new project from scratch → suggest using
/linear-bootstrapor let thelinear-planneragent handle it - Creating 3+ related issues that form an epic → suggest the
linear-planneragent, which will useadd-epic - Planning work with milestones and dependencies → suggest the
linear-planneragent
Patterns
Status checks
- Use
get_projectto get project overview - Use
list_issuesfiltered by project to see issue breakdown by status - Use
get_milestonefor each milestone to check progress - Summarize: % complete, blocked issues, recent activity
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 · 72 lines · 108 tokens per session scan A 0a1744200b32
linear-ops is an agent published in the GitHub repository toolwright-adk/toolwright-monorepo (1 stars, last pushed 5mo ago), licensed MIT. It adds 108 tokens to every session and 687 once invoked, about $0.0005 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
dependency-blocker-monitor
Use when monitoring workcell BOM dependencies and cell health to open or resolve blocker issues when a cell fails or recovers. USE FOR: read workcell BOM dependencies, monitor cell deployment status, create blocker issues, and resolve them on recovery. DO NOT USE FOR: general incident response, application code, or…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.