Borrowing it
Nothing to install: this file belongs to tacticlaunch/mcp-linear. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tacticlaunch/mcp-linear/main/.github/skills/inspect-linear-sdk/SKILL.mdgit clone --depth 1 https://github.com/tacticlaunch/mcp-linearWrote 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/tacticlaunch/mcp-linear/inspect-linear-sdk)<a href="https://agentmods.dev/skills/tacticlaunch/mcp-linear/inspect-linear-sdk"><img src="https://agentmods.dev/badge/skills/tacticlaunch/mcp-linear/inspect-linear-sdk/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/tacticlaunch/mcp-linear/inspect-linear-sdk"><img src="https://agentmods.dev/badge/skills/tacticlaunch/mcp-linear/inspect-linear-sdk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00245 |
| Opus 5.5 | $0.00017 | $0.00098 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (148 stars, last pushed 17d ago), licensed MIT. It adds 43 tokens to every session and 245 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-08-30.
Other skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.