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/tacticlaunch/mcp-linear/inspect-linear-sdknpx skills add tacticlaunch/mcp-linear --skill inspect-linear-sdkgit clone --depth 1 https://github.com/tacticlaunch/mcp-linearWhat 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.00043 | $0.00245 |
| Opus 5 | $0.00022 | $0.00122 |
| Sonnet 5 | $0.00009 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
inspect-linear-sdk 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 3d 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
Use this skill before implementing a new Linear capability.
Inspect these sources first
node_modules/@linear/sdk/dist/_generated_sdk.d.tsnode_modules/@linear/sdk/dist/_generated_documents.d.ts- existing related code in
src/services/linear-service.ts
What to verify
- Whether the capability already has an SDK method.
- The exact mutation or query variable shape.
- The entity class shape and relation getters.
- Which fields are nullable, clearable, enum-based, or paginated.
- Whether the generated SDK query looks stale for the current Linear schema.
Decision rules
- Prefer the SDK when it is correct and complete.
- If the SDK is stale, use a direct GraphQL query only for the missing path and keep it as narrow as possible.
- When you fall back to direct GraphQL, note the mismatch in code comments or the PR summary so future maintainers know why the fallback exists.
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.
- 3d ago First seen · 27 lines · 43 tokens per session scan A d29181c2a66c
inspect-linear-sdk is a skill published in the GitHub repository tacticlaunch/mcp-linear (146 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 245 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-30.
Other skills, from other repositories
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…
firebase-analytics
Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.
firebase-remote-config
Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…
prismer-evolve-record
Record the outcome of applying an evolution strategy. Use after resolving an error where prismer-evolve-analyze provided a recommendation, to feed back success or failure to the network.