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 s09-template-librarygit 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/s09-template-library)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s09-template-library"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s09-template-library/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/s09-template-library"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s09-template-library.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.00097 | $0.02895 |
| Opus 5 | $0.00048 | $0.01448 |
| Sonnet 5 | $0.00019 | $0.00579 |
| Haiku 4.5 | $0.00010 | $0.00290 |
Grade A, and why
harness-template-library scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "<+pipeline.variables.slackWebhook>" \ How it starts
The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Template Library
Purpose
Build a governed library of reusable pipeline building blocks that enforce engineering standards, eliminate copy-paste drift, and allow teams to compose pipelines from pre-approved, versioned templates.
Input Contract
| Input | Source | Required |
|---|---|---|
| Pipeline design patterns | s04 output | Yes |
| Security scan requirements | s01 PRD or user | No |
| Approval gate requirements | s01 (compliance needs) | Yes |
| Notification preferences | s02 taste (communication) | No |
| Service team structures | s05 output | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Deploy stage template | .commandcode/artifacts/template-deploy.yaml |
YAML |
| Security scan step group template | .commandcode/artifacts/template-security.yaml |
YAML |
| Approval stage template | .commandcode/artifacts/template-approval.yaml |
YAML |
| Notification step group template | .commandcode/artifacts/template-notify.yaml |
YAML |
| Template enforcement OPA policy | s22 (governance) | Rego |
| Template version changelog | .commandcode/artifacts/template-changelog.md |
Markdown |
Prerequisites
- Harness account with Template Library access
- Engineering standards documented (what must be identical across all pipelines)
- RBAC roles defined (who can create/modify templates vs use them)
Template Hierarchy
Account-level templates → Shared across ALL orgs and projects
└── Org-level templates → Shared across all projects in org
└── Project-level templates → Used within one project
Template Types:
├── Pipeline Template → Entire pipeline as a template
├── Stage Template → One stage (CI, CD, Approval, etc.)
├── Step Template → One step (Run, ShellScript, etc.)
└── Step Group Template → A group of steps as a unit
Template Versioning Strategy
<template-identifier>
├── v1 — Stable (in use by 20+ pipelines)
├── v2 — Stable (new default)
└── v3 — Beta (testing phase)
Versioning rules:
- Patch (1.0 → 1.1): Non-breaking — add optional fields, fix bugs
- Minor (1.x → 2.0): Breaking — remove fields, change required inputs
- Always keep v_previous stable for 30 days after new version release
- Deprecation: set isStable: false, add deprecation notice in description
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.
- 11d ago First seen · 450 lines · 97 tokens per session scan A 6a27661f2b0f
harness-template-library is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 97 tokens to every session and 2,895 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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.
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/.