pipeline-conductor SKILL.md skillA
pipeline-conductor from chrono-meta/forge-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrono-meta/forge-harness/pipeline-conductor@git:20260912.dbffbe6Pins git:20260912.dbffbe6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrono-meta/forge-harness
- Path
plugins/fh-meta/skills/pipeline-conductor/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260912.dbffbe6, committed Sep 12, 2026
- First version recorded
- Jun 12, 2026
- Size
- 15,844 bytes
- Repository stars
- 31
- License
- MIT
Chains the four core FH verification pipelines (harvest-loop → steel-quench → phantom-quench → sim-conductor) into a single gated sweep. Accepts a scope (single skill, specific asset, full harness) and aggregates results into one structured report. Supports --quick mode (steps 2+3 only) and --full mode (all four steps). Triggered by "run the full pipeline", "chain all verifications", "end-to-end sweep", "pipeline-conductor", or "verify everything".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# pipeline-conductor — Chained Verification Sweep Chains the four standalone FH verification pipelines into a gated sequence. Each step receives the previous step's verdict before proceeding. Aggregates all findings into a single structured report at the end. The gap this closes: harvest-loop, steel-quench, phantom-quench, and sim-conductor are each invocable independently but have no automatic hand-off between them. Running them sequentially by hand loses inter-step signal — a FAIL in step 2 should block step 3 rather than silently continuing. pipeline-conductor enforces that ordering. ## Triggers - `/pipeline-conductor` - "Run the full verification pipeline", "chain all four verifications" - "End-to-end sweep before I push", "verify everything at once" - "I want to run all the checks in order", "do a full harness review" - "Run quench then grounding then sim", "chain the pipelines" - "Full pipeline on this skill", "sweep this asset before release" > **Disambiguation**: "run the pipeline" alone may trigger harvest-loop (which uses identical phrasing). Prefer "run pipeline-conductor" or "chain all verifications" for unambiguous activation. ## Modes …
Read the whole file at its exact version.
How to install
mdr add chrono-meta/forge-harness/pipeline-conductor@sha256:676f9cea11f5e99fThe line at the top of this page pins the label git:20260912.dbffbe6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_gdxysljcpwle6idi)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 12, 2026 and Sep 12, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260912.dbffbe6 latest | 2026-09-12 | dbffbe6 | 15,844 B | A | view · diff |
| git:20260811.52c0a42 | 2026-08-11 | 52c0a42 | 15,843 B | A | view · diff |
| git:20260810.69d1ce6 | 2026-08-10 | 69d1ce6 | 14,875 B | A | view · diff |
| git:20260615.f4d0aef | 2026-06-15 | f4d0aef | 14,357 B | A | view · diff |
| git:20260612.52ea5a0 | 2026-06-12 | 52ea5a0 | 13,392 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15844 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chrono-meta/forge-harness · 31 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gdxysljcpwle6idi GET https://markdownregistry.com/api/v1/resolve?ref=chrono-meta/forge-harness/pipeline-conductor GET https://markdownregistry.com/api/v1/blob/676f9cea11f5e99ffb91660818ffd4dff6c277c3d3e880c04c45c52dd886f886
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.