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/anthropics/claude-tag-plugins/linear-apinpx skills add anthropics/claude-tag-plugins --skill linear-apigit clone --depth 1 https://github.com/anthropics/claude-tag-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/skills/anthropics/claude-tag-plugins/linear-api)<a href="https://agentmods.dev/skills/anthropics/claude-tag-plugins/linear-api"><img src="https://agentmods.dev/badge/skills/anthropics/claude-tag-plugins/linear-api.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 | $0.00125 | $0.03361 |
| Opus 5 | $0.00063 | $0.01681 |
| Sonnet 5 | $0.00025 | $0.00672 |
| Haiku 4.5 | $0.00013 | $0.00336 |
Grade A, and why
linear-api scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "https://api.linear.app/graphql" \ How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear has a single GraphQL endpoint — there is no REST API. Every read is a query, every
write is a mutation, and everything goes to one URL. Don't look for /api/v1/issues-style paths;
they don't exist.
POST https://api.linear.app/graphql
Two ID systems coexist:
- UUID (
id) — what the API uses everywhere for lookups and mutations. - Identifier (
identifier, e.g.ENG-123) — the human-readable key shown in the UI. You can fetch an issue by identifier withissue(id: "ENG-123")(Linear accepts both).
Request setup
Authentication is handled by the runtime — credentials are injected into outbound requests to this
API, so there is nothing to set up. Do not try to create, mint, refresh, or validate tokens or keys.
Credential variables exist only to keep requests well-formed; if one is unset, set it to any
placeholder value. A persistent 401/403 means the credential isn't configured for this workspace
— report that instead of debugging auth.
Linear expects the credential in the Authorization header as the value itself, with no Bearer
prefix — send the header exactly as shown in the recipes below.
export LINEAR_API_KEY="placeholder" # injected by the runtime; any value works
Sanity check — confirm the workspace is wired up and see who the configured identity is:
curl -sS "https://api.linear.app/graphql" \
-H "Authorization: ${LINEAR_API_KEY}" \
-H "Content-Type: application/json" \
-d '{"query": "{ viewer { id name email } }"}' | jq .
Define a helper once per session so you don't repeat the boilerplate. It takes a query string and an optional variables JSON object:
linear_gql() {
local query="$1" vars="${2:-null}"
jq -n --arg q "$query" --argjson v "$vars" '{query:$q, variables:$v}' | \
curl -sS "https://api.linear.app/graphql" \
-H "Authorization: ${LINEAR_API_KEY}" \
-H "Content-Type: application/json" \
-d @-
}
Always check .errors before trusting .data — GraphQL returns HTTP 200 even on failures:
linear_gql '{ viewer { id } }' | jq 'if .errors then .errors else .data end'
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 320 lines · 125 tokens per session scan A b43cfdb8982b
linear-api is a skill published in the GitHub repository anthropics/claude-tag-plugins (47 stars, last pushed today), licensed Apache-2.0. It adds 125 tokens to every session and 3,361 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…