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 skills/agentfront/frontmcp/frontmcp-testingnpx skills add agentfront/frontmcp --skill frontmcp-testinggit clone --depth 1 https://github.com/agentfront/frontmcpWhat 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.00175 | $0.04079 |
| Opus 5 | $0.00088 | $0.02039 |
| Sonnet 5 | $0.00035 | $0.00816 |
| Haiku 4.5 | $0.00017 | $0.00408 |
Grade A, and why
frontmcp-testing scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Test CLI binary builds | `test-cli-binary` | Spawn-and-curl smoke tests for `frontmcp build --target cli` artifacts | How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FrontMCP Testing Router
Entry point for testing FrontMCP applications. This skill helps you navigate testing strategies across component types and find the right patterns for unit, integration, and E2E tests.
When to Use This Skill
Must Use
- Setting up testing infrastructure for a new FrontMCP project
- Deciding how to test a specific component type (tool, resource, prompt, agent)
- Planning a testing strategy that covers unit, E2E, and coverage requirements
Recommended
- Looking up testing patterns for a component type you haven't tested before
- Understanding the relationship between unit tests, E2E tests, and coverage thresholds
- Troubleshooting test failures or coverage gaps
Skip When
- You need detailed Jest configuration and test harness setup (go directly to
setup-testing) - You need to build components, not test them (see
frontmcp-development) - You need to deploy, not test (see
frontmcp-deployment)
Decision: Use this skill for testing strategy and routing. Open the
setup-testingreference underreferences/for hands-on Jest configuration and test writing.
Prerequisites
- A FrontMCP project with at least one component to test (see
frontmcp-development). - Jest installed and configured — if not, start with
setup-testingbefore opening any other testing skill. - The component itself implemented and exported; tests reach decorated classes through the SDK, not by importing internal builders.
Steps
This is a router skill. Follow this order to pick a testing approach, then move to the target reference under references/.
- Pick the test layer — unit (fastest, mock DI), integration (real DI scope), or E2E (real MCP client + server). Use the Testing Strategy table below.
- Pick the component flavour — tool / resource / prompt / agent / job — each has a distinct recipe.
- Pick the runtime concern — auth, browser/CLI build, direct vs streamable transport — and add the matching reference to your reading list.
- Open the target reference (e.g.
references/test-tool-unit.md,references/test-e2e-handler.md,references/test-auth.md) and follow its Steps section. - Enforce coverage — confirm the project's 95%+ thresholds are wired into Jest before merging (see
references/setup-testing.md).
What ships with it
25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/setup-testing/fixture-based-e2e-test.md 2.5 KB
- examples/setup-testing/jest-config-with-coverage.md 1.5 KB
- examples/setup-testing/unit-test-tool-resource-prompt.md 3.3 KB
- examples/test-auth/oauth-flow-test.md 3.0 KB
- examples/test-auth/role-based-access-test.md 3.6 KB
- examples/test-auth/token-factory-test.md 2.9 KB
- examples/test-browser-build/browser-bundle-validation.md 2.0 KB
- examples/test-browser-build/playwright-browser-test.md 2.5 KB
- examples/test-cli-binary/binary-startup-test.md 2.5 KB
- examples/test-cli-binary/js-bundle-import-test.md 1.9 KB
- examples/test-direct-client/basic-create-test.md 2.6 KB
- examples/test-direct-client/openai-claude-format-test.md 2.9 KB
- examples/test-e2e-handler/basic-e2e-test.md 2.6 KB
- examples/test-e2e-handler/manual-client-with-transport.md 2.5 KB
- examples/test-e2e-handler/tool-call-and-error-e2e.md 2.8 KB
- examples/test-tool-unit/basic-tool-test.md 2.2 KB
- examples/test-tool-unit/schema-validation-test.md 2.7 KB
- examples/test-tool-unit/tool-error-handling-test.md 3.1 KB
- references/setup-testing.md 21 KB
- references/test-auth.md 7.1 KB
- references/test-browser-build.md 2.7 KB
- references/test-cli-binary.md 2.3 KB
- references/test-direct-client.md 3.8 KB
- references/test-e2e-handler.md 3.8 KB
- references/test-tool-unit.md 2.7 KB
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.
- 2d ago First seen · 231 lines · 175 tokens per session scan A 891c2ed5417d
frontmcp-testing is a skill published in the GitHub repository agentfront/frontmcp (147 stars, last pushed 26d ago), licensed Apache-2.0. It adds 175 tokens to every session and 4,079 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-generator
Generate comprehensive unit, integration, and end-to-end tests. Use when adding test coverage, writing tests for new features, or improving existing test suites.
Test Engineer
Creates or completes a medium-coverage test suite: unit, component, and critical e2e flows.
test-generation
Generate a test strategy and starter test stubs for given modules across unit, integration, and e2e layers (pytest/jest/playwright). Trigger on: generate tests, test plan, test strategy, coverage plan, test scaffolding.
nestjs-testing
Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.
qa-engineer-agent
QA 工程师 Agent — 测试策略、测试用例设计、自动化测试、性能测试、安全测试.
frontend-testing
Test web frontends (React/Next.js) effectively. Use when writing or fixing unit/component tests with Vitest + Testing Library, end-to-end tests with Playwright, or deciding what to test in a frontend app.