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.
git clone --depth 1 https://github.com/jeffh/claude-pluginsWrote 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/commands/jeffh/claude-plugins/linear)<a href="https://agentmods.dev/commands/jeffh/claude-plugins/linear"><img src="https://agentmods.dev/badge/commands/jeffh/claude-plugins/linear/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.
<a href="https://agentmods.dev/commands/jeffh/claude-plugins/linear"><img src="https://agentmods.dev/badge/commands/jeffh/claude-plugins/linear.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.04088 |
| Opus 5.5 | $0.00006 | $0.01635 |
| Sonnet 5.5 | $0.00003 | $0.00818 |
| Haiku 4.5 | $0.00001 | $0.00409 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear - Ticket Management
You are tasked with managing Linear tickets, including creating tickets from thoughts documents, updating existing tickets, and following the team's specific workflow patterns.
Initial Setup
First, verify that Linear MCP tools are available by checking if any mcp__linear__ tools exist. If not, respond:
I need access to Linear tools to help with ticket management. Please run the `/mcp` command to enable the Linear MCP server, then try again.
If tools are available, respond based on the user's request:
For general requests:
I can help you with Linear tickets. What would you like to do?
1. Create a new ticket from a thoughts document
2. Add a comment to a ticket (I'll use our conversation context)
3. Search for tickets
4. Update ticket status or details
For specific create requests:
I'll help you create a Linear ticket from your thoughts document. Please provide:
1. The path to the thoughts document (or topic to search for)
2. Any specific focus or angle for the ticket (optional)
Then wait for the user's input.
Team Workflow & Status Progression
The team follows a specific workflow to ensure alignment before code implementation:
- Triage → All new tickets start here for initial review
- Spec Needed → More detail is needed - problem to solve and solution outline necessary
- Research Needed → Ticket requires investigation before plan can be written
- Research in Progress → Active research/investigation underway
- Research in Review → Research findings under review (optional step)
- Ready for Plan → Research complete, ticket needs an implementation plan
- Plan in Progress → Actively writing the implementation plan
- Plan in Review → Plan is written and under discussion
- Ready for Dev → Plan approved, ready for implementation
- In Dev → Active development
- Code Review → PR submitted
- Done → Completed
Key principle: Review and alignment happen at the plan stage (not PR stage) to move faster and avoid rework.
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.
- 1mo ago First seen · 389 lines · 14 tokens per session scan A cd2e728579c3
linear is a command published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 10d ago), licensed Apache-2.0. It adds 14 tokens to every session and 4,088 once invoked, about $0.0001 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-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.