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-fix-defectgit 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-fix-defect)<a href="https://agentmods.dev/skills/gongyijie85/dsh-ecc/orch-fix-defect"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/orch-fix-defect/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-fix-defect"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/orch-fix-defect.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.00051 | $0.00437 |
| Opus 5 | $0.00026 | $0.00218 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
orch-fix-defect 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-fix-defect — 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-fix-defect
Actor · action · target: orch · fix · defect. Thin wrapper over the shared
engine in orch-pipeline.
When to Use
- Something is broken: wrong output, an error, a crash, a regression.
- Distinguish from siblings:
- behavior is correct but you want it different →
orch-change-feature. - the capability does not exist yet →
orch-add-feature.
- behavior is correct but you want it different →
Operation settings
- Default size floor: small (often trivial).
- Phase mask: 0 → (light 2 only if root cause is non-obvious or standard+) → 4 → 5 → 6. Research (1) is usually skipped.
- First move (phase 4): reproduce the bug as a new failing test (regression test), then fix until it goes green. Proving the bug exists first is what separates a fix from a tweak.
How It Works
- Run the
orch-pipelineengine with the settings above. - If the root cause is unclear, scope it with
code-explorerbefore the red test; escalate build breaks tobuild-error-resolver//build-fix. - Stop at Gate 1 (only if a plan was produced) and Gate 2 (pre-commit).
- Add
security-reviewerif the defect sits in a security-sensitive path.
Example
orch-fix-defect: poller crashes on empty NWS response
→ write failing test reproducing the crash → fix to green
→ code-review → commit [GATE 2: confirm] (commit: fix:)
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 · 44 lines · 51 tokens per session scan A 399e142bbf37
orch-fix-defect is a skill published in the GitHub repository gongyijie85/dsh-ecc (7 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 437 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-fix-defect, 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.
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.