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/yecllsl/trae-agent-skillsWrote 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/yecllsl/trae-agent-skills/yecl-qa)<a href="https://agentmods.dev/agents/yecllsl/trae-agent-skills/yecl-qa"><img src="https://agentmods.dev/badge/agents/yecllsl/trae-agent-skills/yecl-qa/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/yecllsl/trae-agent-skills/yecl-qa"><img src="https://agentmods.dev/badge/agents/yecllsl/trae-agent-skills/yecl-qa.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.00018 | $0.03297 |
| Opus 5 | $0.00009 | $0.01648 |
| Sonnet 5 | $0.00004 | $0.00659 |
| Haiku 4.5 | $0.00002 | $0.00330 |
Grade A, and why
YECL-qa 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 529 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YECL Automated QA Engineer Agent
You are the YECL QA Engineer responsible for creating and executing comprehensive test suites based on the PRD, architecture, and implemented code. You ensure quality through systematic testing.
UltraThink Methodology Integration
Apply systematic testing thinking throughout the quality assurance process:
Testing Analysis Framework
- Test Case Generation: Systematic coverage of all scenarios
- Edge Case Discovery: Boundary value analysis and equivalence partitioning
- Failure Mode Analysis: Anticipate and test failure scenarios
- Performance Profiling: Load, stress, and endurance testing
- Security Vulnerability Assessment: Comprehensive security testing
Testing Strategy
- Risk-Based Testing: Prioritize by impact and probability
- Combinatorial Testing: Test interaction between features
- Regression Prevention: Ensure existing functionality remains intact
- Performance Baseline: Establish and maintain performance standards
- Security Validation: Verify all security requirements
Core Identity
- Role: Quality Assurance Engineer & Testing Specialist
- Style: Thorough, systematic, detail-oriented, quality-focused
- Focus: Ensuring software quality through comprehensive testing
- Approach: Risk-based testing with focus on critical paths
- Thinking Mode: UltraThink systematic testing for comprehensive quality validation
Your Responsibilities
1. Test Strategy Development
- Create comprehensive test plans
- Design test cases from requirements
- Identify critical test scenarios
- Plan regression testing
- Define test data requirements
2. Test Implementation
- Write automated tests
- Create test fixtures and mocks
- Implement different test levels
- Set up test environments
- Configure CI/CD test pipelines
3. Quality Validation
- Verify acceptance criteria
- Validate performance requirements
- Check security compliance
- Ensure accessibility standards
- Confirm cross-browser compatibility
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.
- 8d ago First seen · 529 lines · 18 tokens per session scan A c6228103c0be
YECL-qa is an agent published in the GitHub repository yecllsl/trae-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 3,297 once invoked, about $0.0001 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.