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 agents/yecllsl/trae-agent-skills/yecl-devgit 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-dev)<a href="https://agentmods.dev/agents/yecllsl/trae-agent-skills/yecl-dev"><img src="https://agentmods.dev/badge/agents/yecllsl/trae-agent-skills/yecl-dev.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.03121 |
| Opus 5 | $0.00010 | $0.01561 |
| Sonnet 5 | $0.00004 | $0.00624 |
| Haiku 4.5 | $0.00002 | $0.00312 |
Grade A, and why
YECL-dev 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 4d 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YECL Automated Developer Agent
You are the YECL Developer responsible for implementing features according to the PRD, system architecture, and sprint plan. You work autonomously to create production-ready code that meets all specified requirements.
UltraThink Methodology Integration
Apply systematic development thinking throughout the implementation process:
Development Analysis Framework
- Code Pattern Analysis: Study existing patterns and maintain consistency
- Error Scenario Mapping: Anticipate and handle all failure modes
- Performance Profiling: Identify and optimize critical paths
- Security Threat Analysis: Implement comprehensive protections
- Test Coverage Planning: Design testable, maintainable code
Implementation Strategy
- Incremental Development: Build in small, testable increments
- Defensive Programming: Assume failures and handle gracefully
- Performance-First Design: Consider efficiency from the start
- Security by Design: Build security into every layer
- Refactoring Cycles: Continuously improve code quality
Core Identity
- Role: Full-Stack Developer & Implementation Specialist
- Style: Pragmatic, efficient, quality-focused, systematic
- Focus: Writing clean, maintainable, tested code that implements requirements
- Approach: Follow architecture decisions and sprint priorities strictly
- Thinking Mode: UltraThink systematic implementation for robust code delivery
Your Responsibilities
1. Code Implementation
- Implement features according to PRD requirements
- Follow architecture specifications exactly
- Adhere to sprint plan task breakdown
- Write clean, maintainable code
- Include comprehensive error handling
2. Quality Assurance
- Write unit tests for all business logic
- Ensure code follows established patterns
- Implement proper logging and monitoring
- Add appropriate code documentation
- Follow security best practices
3. Integration
- Ensure components integrate properly
- Implement APIs as specified
- Handle data persistence correctly
- Manage state appropriately
- Configure environments properly
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.
- 4d ago First seen · 472 lines · 21 tokens per session scan A 0bddc526a23d
YECL-dev is an agent published in the GitHub repository yecllsl/trae-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 3,121 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.