Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jakyeamos/tmcpnpx agentmods add skills/jakyeamos/tmcp/tmcp-test-strategyWrote 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/jakyeamos/tmcp/tmcp-test-strategy)<a href="https://agentmods.dev/skills/jakyeamos/tmcp/tmcp-test-strategy"><img src="https://agentmods.dev/badge/skills/jakyeamos/tmcp/tmcp-test-strategy/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/jakyeamos/tmcp/tmcp-test-strategy"><img src="https://agentmods.dev/badge/skills/jakyeamos/tmcp/tmcp-test-strategy.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.00031 | $0.00296 |
| Opus 5 | $0.00015 | $0.00148 |
| Sonnet 5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
tmcp-test-strategy 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 9d 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
TMCP Test Strategy
Status: experimental. This workflow remains shipped and callable, but its public contract may change.
Use this skill when the user asks what to test, whether tests are valuable, how to cover regression risk, whether coverage protects behavior, or how to improve a test/quality gate plan.
Do not use it to debug a failing test unless the user asks for a test strategy or regression-risk packet.
Workflow
- Gather evidence: public contracts, domain rules, recent bugs, test files, CI checks, coverage reports, and quality-gate requirements.
- Invoke
tmcp_explainfor the testing packet. - Invoke
expert_rubric_review_planfor a scored test strategy and remediation plan. - If MCP tools are unavailable, run from the TMCP plugin root:
node scripts/tmcp_launcher.mjs review-plan "Review test strategy and regression risk for <project>" --project-path "<project-path>" --evidence-json '<json>' --write-artifacts
Output Contract
Produce or cite:
- TMCP packet and
substance_check. - Behavior and contract coverage map.
- Regression-risk gaps.
- Low-value or redundant test findings.
- Verification-focused remediation plan.
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.
- 9d ago First seen · 35 lines · 31 tokens per session scan A 0e25ff48438a
tmcp-test-strategy is a skill published in the GitHub repository jakyeamos/tmcp (0 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 296 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-31.
Other skills, from other repositories
python-pro
Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns…
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
test-corpus
The testdocuments submodule is a bucket-fetched fixture corpus that is not committed. This skill covers readtestfixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing…