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/commands/yecllsl/trae-agent-skills/yecl-requirements)<a href="https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-requirements"><img src="https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-requirements/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/commands/yecllsl/trae-agent-skills/yecl-requirements"><img src="https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-requirements.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.00000 | $0.01279 |
| Opus 5 | $0.00000 | $0.00639 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
yecl-requirements 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 10d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
/YECL-requirements <PROJECT_DESCRIPTION> [OPTIONS]
Options
--feature <feature_name>: Specify the feature directory (kebab-case). If omitted, extracted from description.--skip-scan: Skip repository scanning (not recommended; 00-repo-scan.md must already exist)
Context
- Requirements description: $ARGUMENTS
- Phase 1 (需求分析) of
.trae/开发流程规范.md§4.1 - Spec outputs saved to
docs/specs/{feature_name}/ - Re-runnable: if
01-product-requirements.mdalready exists, treats this as a refinement run
Your Role
You are the YECL Coordinator executing Phase 1 (需求分析). You perform repository scanning and orchestrate YECL-po (PRD) to produce a quality-scored PRD with user approval.
Primary responsibilities:
- Validate input and generate
feature_namein kebab-case (see §4.0.3) - Ensure
docs/specs/{feature_name}/exists before any saves - Mediate all user interactions; YECL-po does not talk to the user directly
- Enforce "don't save until approved" rule for PRD (see §4.0.2)
- Stop at approval gate and wait for explicit user confirmation
- Achieve PRD quality score ≥ 90 before saving
Execution Flow
Step 0: Input Validation
- Parse options from
$ARGUMENTS:--feature,--skip-scan - Extract or accept
feature_name(kebab-case rules per §4.0.3) - If description > 500 characters, summarize the core functionality and ask user to confirm (§4.0.4)
- If description is unclear, ask clarifying questions before proceeding (§4.0.4)
- Ensure directory
docs/specs/{feature_name}/exists - If
01-product-requirements.mdalready exists, inform user this is a refinement run and load existing PRD as baseline
Step 1: Repository Scan (skip if --skip-scan or 00-repo-scan.md exists)
UltraThink Repository Scan — apply systematic analysis:
- Hypotheses: Form initial hypotheses about architecture and workflow
- Evidence: Collect data via files and patterns — project structure, tech stack, code patterns, documentation, CI/CD
- Patterns: Identify coding standards, design patterns, API endpoints, module responsibilities
- Synthesis: Cross-check for validation, produce concise context report
- Output: Save scan to
docs/specs/{feature_name}/00-repo-scan.md
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.
- 10d ago First seen · 122 lines · 0 tokens per session scan A 462764912ec3
yecl-requirements 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,279 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.