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/agents/mcp-live-tester.agent.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/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/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/agents/tacticlaunch/mcp-linear/mcp-live-tester"><img src="https://agentmods.dev/badge/agents/tacticlaunch/mcp-linear/mcp-live-tester.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.00208 |
| Opus 5.5 | $0.00010 | $0.00083 |
| Sonnet 5.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 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
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.
- 2mo 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 (148 stars, last pushed 17d ago), licensed MIT. It adds 25 tokens to every session and 208 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 agents, from other repositories
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
f1-test-drive
Assess applicability and run relevant F1 scenarios for changed product workflows or F1 harness behavior. Do not run drives or create reports for nonapplicable changes.
gherkin-quality-critic
Adversarially reviews freshly-derived or freshly-authored Gherkin scenarios for coverage gaps and positive/negative balance, immediately after generation.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.