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 dungnotnull/hybrid-harness-chaos-process-prm --skill s04-pipeline-designgit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s04-pipeline-design)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s04-pipeline-design"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s04-pipeline-design/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/dungnotnull/hybrid-harness-chaos-process-prm/s04-pipeline-design"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s04-pipeline-design.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.00112 | $0.02931 |
| Opus 5 | $0.00056 | $0.01465 |
| Sonnet 5 | $0.00022 | $0.00586 |
| Haiku 4.5 | $0.00011 | $0.00293 |
Grade A, and why
harness-pipeline-design 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 12d 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Pipeline Design
Purpose
Produce complete, schema-valid Harness pipeline YAML that follows enterprise engineering standards: parameterized inputs, environment promotion, integrated verification, and chaos-ready stage structure.
Input Contract
| Input | Source | Required |
|---|---|---|
| PRD / BA analysis output | s01 (workflow_context.prd) | Yes |
| Service name, artifact source, stack info | s01 context | Yes |
| Environment tier list (dev/staging/prod) | s01 context or user | Yes |
| Deploy strategy preference | s02 taste (deployment category) | No (defaults to Rolling) |
| Approval mechanism preference | s02 taste (risk_tolerance) | No |
| Observability tool preference | s02 taste (observability) | No |
| Harness account/project identifiers | User or CLAUDE.md | Yes |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Pipeline YAML | .commandcode/artifacts/pipeline-<service>.yaml |
YAML |
| Trigger config YAML | .commandcode/artifacts/trigger-<service>.yaml |
YAML |
| Pipeline context (for s05, s12, s19) | workflow_context.artifacts | YAML object |
| Input set templates per env | .commandcode/artifacts/inputset-<env>.yaml |
YAML |
Prerequisites
Before generating any pipeline, confirm:
- Harness Account ID and Organization / Project identifiers known
- Target deployment type: Kubernetes / ECS / Lambda / VM / Custom
- Artifact source: Docker registry / ECR / GCR / Nexus / Artifactory
- Environment tiers required: dev → staging → preprod → prod
- Approval mechanism: automatic / manual / JIRA / ServiceNow
- Observability stack: Prometheus / Datadog / New Relic / AppDynamics
If any item is unknown, surface a question to the user before generating YAML.
Pipeline Anatomy
Pipeline
├── Variables (runtime inputs, expressions)
├── Stages
│ ├── CI Stage (Build + Test + Push)
│ │ ├── Steps: Clone → Build → Unit Test → SAST → Push
│ │ └── Caching: Intelligence cache / S3 cache
│ ├── CD Stage (Deploy)
│ │ ├── Service (artifact + manifests)
│ │ ├── Environment (infrastructure definition)
│ │ ├── Execution
│ │ │ ├── Pre-deployment: secrets sync, DB migration
│ │ │ ├── Deploy step: Rolling / Canary / Blue-Green
│ │ │ ├── Chaos step (optional, see chaos/01-experiment-design)
│ │ │ └── Verify step (CV — see harness/06-cv-verification)
│ │ └── Rollback (auto on failure)
│ └── Approval Stage (between envs)
└── Notification Rules (Slack / email / PagerDuty)
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.
- 12d ago First seen · 405 lines · 112 tokens per session scan A e1548a2d4743
harness-pipeline-design is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 112 tokens to every session and 2,931 once invoked, about $0.0006 per session on Opus 5. 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-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.