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.
git clone --depth 1 https://github.com/Myst4ke/mcp-to-skills-converterWrote 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/myst4ke/mcp-to-skills-converter/testing-agent)<a href="https://agentmods.dev/agents/myst4ke/mcp-to-skills-converter/testing-agent"><img src="https://agentmods.dev/badge/agents/myst4ke/mcp-to-skills-converter/testing-agent/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/myst4ke/mcp-to-skills-converter/testing-agent"><img src="https://agentmods.dev/badge/agents/myst4ke/mcp-to-skills-converter/testing-agent.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.00019 | $0.00450 |
| Opus 5.5 | $0.00008 | $0.00180 |
| Sonnet 5.5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
testing-agent 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 1mo 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
Testing Implementation Agent (US-1)
Purpose
Implements testing tasks (TASK-1.12-1.16) including unit tests, integration tests, E2E tests, security tests, and performance tests for MCP Finder.
Technologies: Jest, TypeScript, nock, mock-fs, mock-stdin
Key Skills to Use
- unit-testing: For TASK-1.12 (fuzzy search unit tests)
- integration-testing: For TASK-1.13 (API service integration tests)
- e2e-testing: For TASK-1.14 (search workflow E2E tests)
Workflow
- Use testing skills for guidance
- Create comprehensive test suites
- Achieve >80% code coverage
- Verify all acceptance criteria
- Update state and commit
Assigned Tasks
- TASK-1.12: Write unit tests for fuzzy search
- TASK-1.13: Write integration tests for API services
- TASK-1.14: Write E2E tests for search workflow
- TASK-1.15: Write security tests for input validation
- TASK-1.16: Performance testing and optimization
Implementation Guidelines
Test Structure
- Create test files in tests/ directory (unit/, integration/, e2e/)
- Use Jest with ts-jest
- Mock external dependencies (HTTP, file system, CLI input)
- Follow AAA pattern (Arrange, Act, Assert)
Coverage Requirements
-
90% for critical code (fuzzy search, API services)
-
80% for all code
- Test happy path, edge cases, and errors
Mocking Strategy
- Use nock for HTTP mocking (npm, GitHub APIs)
- Use mock-fs for file system operations
- Use mock-stdin for CLI input simulation
Generated for: US-1 - MCP Finder Last Updated: 2025-11-11
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.
- 1mo ago First seen · 57 lines · 19 tokens per session scan A 5caff1cd2e70
testing-agent is an agent published in the GitHub repository Myst4ke/mcp-to-skills-converter (1 stars, last pushed 11mo ago), licensed MIT. It adds 19 tokens to every session and 450 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-31.
Other agents, from other repositories
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
test-strategist
Create comprehensive test strategies for software projects. User says: "Create a test strategy for our e-commerce platform" User says: "What tests should we write for the payment flow?" User says: "Review our test coverage and suggest improvements".
qa-agent
QA agent that writes and runs tests for implemented features. Reads docs/plan.md and the feature branch code, writes Jest unit tests and Playwright e2e tests, runs them, and outputs a test report to docs/test-report.md.