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 skills add ulises-jeremias/agent-toolkit --skill lineargit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/linear)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/linear"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/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/skills/ulises-jeremias/agent-toolkit/linear"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/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.00046 | $0.01336 |
| Opus 5.5 | $0.00018 | $0.00534 |
| Sonnet 5.5 | $0.00009 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00134 |
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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear
Structured workflow for managing Linear issues, projects and cycles through the
official Linear MCP server (https://mcp.linear.app/mcp, OAuth).
This skill assumes the MCP is wired into your AI tool. See
docs/MCP.md and
~/.local/share/agent-toolkit/mcp/linear/ for the managed template.
When to use
- "Open a Linear ticket for X", "triage open bugs", "plan the next cycle".
- Sprint/cycle planning, retrospectives, documentation audits.
- Cross-project dependency review or workload rebalancing.
- Any natural-language request that maps onto Linear's MCP toolset.
Prerequisites
- Linear MCP server connected via OAuth in your AI tool of choice.
- Workspace access to the relevant teams and projects.
- agent-toolkit template available at
~/.local/share/agent-toolkit/mcp/linear/(deployed bychezmoi apply).
Setup (per AI tool)
The Linear MCP is a streamable HTTP endpoint with OAuth. Register it in your AI tool of choice using the agent-toolkit template as reference:
| AI tool | Where to register |
|---|---|
| Claude Code | ~/.claude/mcp.json (or via claude mcp add) |
| Cursor | ~/.cursor/mcp.json |
| OpenCode | ~/.config/opencode/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
Copy ~/.local/share/agent-toolkit/mcp/linear/config.template.json into the right
location and follow the OAuth prompt the first time you call a Linear tool.
Windows / WSL note: if direct connections fail on Windows, run the MCP through WSL using
npx -y mcp-remote https://mcp.linear.app/sse --transport sse-onlyas the command. The template includes a comment block with this fallback.
Required workflow
Follow the steps in order. Do not skip read-before-write.
Step 1 — Clarify scope
Confirm with the user:
- Team / project / cycle in scope.
- Goal (triage, planning, audit, rebalance, release planning).
- Filters that matter (priority, label, assignee, status).
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 · 135 lines · 46 tokens per session scan A 66e88d6b899e
linear is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,336 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…
create-jira-item
Create Jira issues (stories, epics, initiatives) with custom field introspection to fill org-specific fields correctly. Use when the user asks to create a Jira ticket, story, epic, initiative, or task.
implement-plan
Use when the user wants to execute an approved implementation plan and says any of "do it" (with a plan in scope), "lets do it" / "let's do it", "confirmed" (as approval to proceed on a plan), "implement the plan", "implement this", "execute the plan", "start implementing", "work through the plan", "implement the next…
breaking-down-work
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a deliverable, or build a work breakdown…
capturing-meeting-actions
Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this".
mapping-dependencies
Maps task dependencies in an Astravue project, finds the critical path and blocked work, and detects circular dependencies before any rescheduling. Use when the user asks about dependencies, blockers, what's blocking what, the critical path, or wants to understand or fix the sequencing of a project.