What is yecl-deployment?

A deployment command for a feature in the YECL development workflow. It checks versions, updates the change log, handles Git and CI steps, and creates a release tag when the checks pass.

Use it to deploy a tested feature, optionally specifying its directory and version, while enforcing the project's merge and CI checks.

It organizes the release steps and catches missing testing, inconsistent version numbers, or failed CI before tagging.

yecl-deployment — 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-deployment/github.svg)](https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-deployment)

Your own site

<a href="https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-deployment"><img src="https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-deployment/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-deployment"><img src="https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-deployment.svg" alt="Reviewed on agentmods" width="80" 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,223 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.01223
Opus 5	$0.00000	$0.00611
Sonnet 5	$0.00000	$0.00245
Haiku 4.5	$0.00000	$0.00122

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

Security

Grade A, and why

yecl-deployment 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.

.trae/commands/yecl-deployment.md · 154 lines

How it starts

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

Usage

/YECL-deployment [OPTIONS]

Options

--feature <feature_name>: Specify the feature directory (required if not inferable from context)
--version <x.y.z>: Specify version number (e.g., 1.2.0). If omitted, prompt user.
--skip-ci: Skip CI/CD wait (not recommended; assumes CI already green)

Context

Phase 5 (部署) of .trae/开发流程规范.md §4.5
Prerequisites: tested code from /YECL-testing + 05-test-report.md
Orchestrator (Coordinator) directly executes git/CI operations
Version consistency required across pyproject.toml / README.md / CHANGELOG.md

Your Role

You are the YECL Coordinator executing Phase 5 (部署). You perform version consistency checks, update CHANGELOG, execute git operations, wait for CI, and create tags.

Primary responsibilities:

Verify testing prerequisites exist
Enforce version number consistency across three files
Update CHANGELOG.md (mandatory)
Execute git operations safely (no force-push main, no skip CI for tags)
Wait for CI to pass before tagging
Enforce merge gate (门控4: 合并前)

Execution Flow

Step 0: Input Validation

Parse options: --feature, --version, --skip-ci
Determine feature_name from --feature option or context
Verify prerequisites exist:
- docs/specs/{feature_name}/05-test-report.md (test report)
- If missing, report error and recommend running /YECL-testing first
Determine version number from --version or prompt user

Step 1: Version Consistency Check

Verify version number is identical across:

pyproject.toml (or package.json / Cargo.toml as applicable)
README.md (version badge or section)
CHANGELOG.md (new version entry)

If inconsistent, update all three to the target version before proceeding.

Step 2: Update CHANGELOG.md (Mandatory)

Add a new version entry to CHANGELOG.md following Keep a Changelog format:

## [{version}] - {YYYY-MM-DD}

### 新增
- [Feature summary from PRD]

### 变更
- [Change summary from development]

### 修复
- [Bug fixes from QA phase]

Read the full file on GitHub · 154 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.

8d ago First seen · 154 lines · 0 tokens per session scan A dd52e90c5ec9

Subscribe to this mod's changes

yecl-deployment 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,223 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.

Cloud DevOps and cloud Git and workflow Releases

yecl-deployment