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 skills add gongyijie85/dsh-ecc --skill orch-add-featuregit clone --depth 1 https://github.com/gongyijie85/dsh-eccWrote 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/skills/gongyijie85/dsh-ecc/orch-add-feature)<a href="https://agentmods.dev/skills/gongyijie85/dsh-ecc/orch-add-feature"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/orch-add-feature/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/skills/gongyijie85/dsh-ecc/orch-add-feature"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/orch-add-feature.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.00052 | $0.00464 |
| Opus 5 | $0.00026 | $0.00232 |
| Sonnet 5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
orch-add-feature 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.
This is a copy
100% identical to orch-add-feature — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
orch-add-feature
Actor · action · target: orch · add · feature. Thin wrapper over the shared
engine in orch-pipeline.
When to Use
- The user wants a capability that does not exist yet ("add", "build", "implement", "support …").
- It is net-new behavior — not a correction (
orch-fix-defect) and not an alteration of existing behavior (orch-change-feature).
Operation settings
- Default size floor: standard — run Research + Plan unless clearly small.
- Phase mask: 0 → 1 → 2 → 4 → 5 → 6 (skip 3 Scaffold; that is MVP-only).
- First move (phase 4): write new failing tests for the new behavior, then implement to green.
How It Works
- Run the
orch-pipelineengine with the settings above. - Classify size first; small / trivial features collapse toward 4 → 5 → 6.
- Stop at Gate 1 (plan approval) and Gate 2 (pre-commit).
- Add
security-reviewerif the feature touches a security trigger.
Related:
/feature-devis a standalone version of this flow.orch-add-featurediffers by sharing theorch-pipelineengine — the size classifier and the two gates — with the rest of the family, so it right-sizes trivial features to 4 → 5 → 6.
Example
orch-add-feature: add OAuth2 login to nws-poller
→ research existing auth libs → plan task_list [GATE 1: approve]
→ TDD each task → code-review (+ security-reviewer: auth path)
→ commit [GATE 2: confirm]
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 · 46 lines · 52 tokens per session scan A 6ba858d94cfa
orch-add-feature is a skill published in the GitHub repository gongyijie85/dsh-ecc (7 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 464 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to orch-add-feature, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
red-green-tdd
Red/green test discipline for implementation work. Use once a doublecheck spec is on record and implementation is about to start — write a test that fails for the missing behavior, run it to see it fail (red), make the change, run again to see it pass (green).
tdd-zh
A test-first development guide for building features or fixing bugs. Test-driven development, or TDD, means writing a test that fails, making it pass with the smallest change, and then improving the code.
implement-zh
An implementation workflow for completing work described in a specification or tickets. It encourages test-first development where appropriate, runs checks during the work, and ends with review and a commit.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…