What is yecl-testing?

A command for coordinating software testing in the YECL development process.

Use it to run unit, integration, end-to-end, security, performance, and accessibility testing, with options to skip end-to-end or security checks.

It checks that implementation and review are complete, then organizes tests and the bug-fix loop before completion is declared.

yecl-testing — Command for Claude Code by yecllsl

Install

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.

Clone the repo

git clone --depth 1 https://github.com/yecllsl/trae-agent-skills

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-testing.svg)](https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-testing)

Your own site

<a href="https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-testing"><img src="https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-testing.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,219 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.01219
Opus 5	$0.00000	$0.00609
Sonnet 5	$0.00000	$0.00244
Haiku 4.5	$0.00000	$0.00122

Measured 6d ago against content hash 736773b1c803, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

yecl-testing 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 6d 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.

.trae/commands/yecl-testing.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Usage

/YECL-testing [OPTIONS]

Options

--feature <feature_name>: Specify the feature directory (required if not inferable from context)
--skip-e2e: Skip E2E tests (unit + integration only)
--skip-security: Skip security testing

Context

Phase 4 (测试) of .trae/开发流程规范.md §4.4
Prerequisites: implemented code from /YECL-development + 04-dev-reviewed.md
Orchestrator mediation: YECL-qa communicates through Coordinator
YECL-qa has Playwright MCP enabled (E2E testing preferred)
Test pyramid: Unit 70% / Integration 20% / E2E 10%

Your Role

You are the YECL Coordinator executing Phase 4 (测试). You orchestrate YECL-qa to validate functionality, performance, security, and accessibility, and manage the bug-fix loop with YECL-dev.

Primary responsibilities:

Verify development prerequisites exist
Mediate between QA and Dev during bug-fix loops
Enforce test pyramid and coverage thresholds
Manage bug-fix escalation (loop >3 → return to planning)
Verify test suite passes before declaring completion

Execution Flow

Step 0: Input Validation

Parse options: --feature, --skip-e2e, --skip-security
Determine feature_name from --feature option or context
Verify prerequisites exist:
- docs/specs/{feature_name}/01-product-requirements.md
- docs/specs/{feature_name}/02-system-architecture.md
- docs/specs/{feature_name}/04-dev-reviewed.md (review report)
- Implemented source code
- If missing, report error and recommend running /YECL-development first

Step 1: QA Test Strategy & Execution (via YECL-qa)

Use Task tool with YECL-qa agent:

Repository Context: [test patterns from 00-repo-scan.md]
Feature Name: {feature_name}
Working Directory: {project_root}
Skip E2E: {true/false based on --skip-e2e}
Skip Security: {true/false based on --skip-security}

Task: Create and execute comprehensive test suite
Instructions:
1. Read PRD, Architecture, Sprint Plan, and Review Report from docs/specs/{feature_name}/
2. Review implemented code from development phase
3. Create comprehensive test suite validating all acceptance criteria:
   - Functional tests: core business logic + boundary values + error scenarios
   - Integration tests: component interactions + API endpoints
   - Performance tests: response time + concurrent load
   - Security tests: SQL injection / XSS / auth bypass (unless --skip-security)
   - Accessibility tests: ARIA labels + keyboard navigation
   - E2E tests via Playwright (unless --skip-e2e)
4. Focus on risk areas flagged in the review report
5. Execute tests and report results
6. Ensure quality standards are met (coverage thresholds)

Read the full file on GitHub · 129 lines

Changes

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.

6d ago First seen · 129 lines · 0 tokens per session scan A 736773b1c803

Subscribe to this mod's changes

yecl-testing is a command published in the GitHub repository yecllsl/trae-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,219 tokens. 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.

Testing

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

yecl-testing