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/live-linear-smoke/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/live-linear-smoke)<a href="https://agentmods.dev/skills/tacticlaunch/mcp-linear/live-linear-smoke"><img src="https://agentmods.dev/badge/skills/tacticlaunch/mcp-linear/live-linear-smoke/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/live-linear-smoke"><img src="https://agentmods.dev/badge/skills/tacticlaunch/mcp-linear/live-linear-smoke.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.00035 | $0.00200 |
| Opus 5.5 | $0.00014 | $0.00080 |
| Sonnet 5.5 | $0.00007 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
live-linear-smoke 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 for live validation of MCP tool changes.
Preconditions
- Local build and unit tests should already pass.
- Linear credentials or an existing local MCP client setup must be available.
Workflow
- Run
npm test. - Run
npm run build. - Choose the smallest live scenario that exercises the changed capability.
- Use temporary resource names such as
Smoke Test ...with a timestamp. - Validate both the Linear side effect and the returned normalized payload shape.
- Delete or revert all temporary Linear resources before finishing.
Reporting
- State which live tool calls succeeded.
- State which temporary entities were created and confirm cleanup.
- If a live failure occurs, identify whether it is caused by repo code, SDK drift, or workspace/schema behavior.
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 · 35 tokens per session scan A 1814ca801713
live-linear-smoke is a skill published in the GitHub repository tacticlaunch/mcp-linear (148 stars, last pushed 17d ago), licensed MIT. It adds 35 tokens to every session and 200 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 skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
writing-livekit-scenarios
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my…
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
shared/tdd
A test-driven development guide, where tests are written before the production code and drive the implementation.