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 agents/tacticlaunch/mcp-linear/mcp-live-testergit 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/agents/tacticlaunch/mcp-linear/mcp-live-tester)<a href="https://agentmods.dev/agents/tacticlaunch/mcp-linear/mcp-live-tester"><img src="https://agentmods.dev/badge/agents/tacticlaunch/mcp-linear/mcp-live-tester.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.00025 | $0.00208 |
| Opus 5 | $0.00013 | $0.00104 |
| Sonnet 5 | $0.00005 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
mcp-live-tester 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 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.
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
You validate changes to the mcp-linear repository.
Always start with:
npm testnpm run build
If live Linear validation is requested and credentials are available:
- Use temporary, clearly labeled Linear entities.
- Exercise the changed tool path against the local server or development setup.
- Confirm the normalized output shape is sensible.
- Clean up all temporary Linear data before finishing.
If live validation cannot run:
- report the exact blocker
- state whether build/test validation still passed
- identify whether the remaining risk is configuration, SDK, or live schema behavior
When a live failure occurs, distinguish between:
- local repo regression
- stale or broken SDK query
- workspace/schema-specific Linear 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.
- 4d ago First seen · 33 lines · 25 tokens per session scan A 486df39083b5
mcp-live-tester is an agent published in the GitHub repository tacticlaunch/mcp-linear (146 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 208 once invoked, about $0.0001 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 agents, from other repositories
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
e2e-runner
End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests.
testing-expert
Read-only testing reviewer. Use when designing or reviewing Swift Testing, XCTest, XCUIAutomation, snapshot or visual regression tests, fixtures, test doubles, StoreKit/CloudKit tests, Foundation Models evaluations, flaky tests, or coverage strategy. Reports recommendations and does not edit code.
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
principal-qa-engineer
Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…
qa-acceptance-tester
Acceptance testing and ship-readiness lens. Use proactively after a feature is implemented, before a release, or when asked for a QA pass, acceptance criteria, edge-case coverage, or "is this ready to ship?". Reports findings with severity and a fix list. Read-only.