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 harness/harness-ai --skill manage-freeze-windowsgit clone --depth 1 https://github.com/harness/harness-aiWrote 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/harness/harness-ai/manage-freeze-windows)<a href="https://agentmods.dev/skills/harness/harness-ai/manage-freeze-windows"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/manage-freeze-windows/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/harness/harness-ai/manage-freeze-windows"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/manage-freeze-windows.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.00106 | $0.02662 |
| Opus 5 | $0.00053 | $0.01331 |
| Sonnet 5 | $0.00021 | $0.00532 |
| Haiku 4.5 | $0.00011 | $0.00266 |
Grade A, and why
manage-freeze-windows 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 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.
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 manage-freeze-windows — 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.
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Freeze Windows
Create and toggle Harness deployment freeze windows via MCP. A freeze window blocks pipeline executions within a time window so you can enforce change freezes for releases, holidays, or maintenance.
MCP Tools Used
| Tool | Resource Type | Purpose |
|---|---|---|
harness_list |
freeze_window |
List project freeze windows, filter by status / time / keyword |
harness_get |
freeze_window |
Get a single freeze window by identifier |
harness_create |
freeze_window |
Create a freeze window from YAML |
harness_update |
freeze_window |
Replace an existing freeze window's YAML definition |
harness_delete |
freeze_window |
Delete a freeze window |
harness_execute (action: toggle_status) |
freeze_window |
Enable / disable one or more freeze windows in bulk |
harness_get |
global_freeze |
Get the current project-level global freeze state |
harness_execute (action: manage) |
global_freeze |
Enable or disable the project global freeze from YAML |
harness_schema |
freeze_window |
Exact JSON Schema for the create / update body |
Both resources are project-scoped — every call needs org_id and project_id.
Freeze Window YAML
Create/update bodies take a raw freeze YAML string passed as body: { yaml: "<yaml string>" }. The MCP server forwards it to the Harness API with Content-Type: application/yaml.
freeze:
name: Q4 Release Freeze
identifier: q4_release_freeze
entityConfigs:
- name: All Services
entities:
- type: Service
filterType: All
- type: Environment
filterType: All
- type: EnvType
filterType: All
- type: Org
filterType: All
- type: Project
filterType: All
status: Enabled # Enabled | Disabled
description: "Change freeze for Q4 GA release"
windows:
- timeZone: America/Los_Angeles
startTime: 2026-12-20 00:00 AM
duration: 14d # e.g. 2h, 3d, 14d, 4w
recurrence:
type: Yearly # Daily | Weekly | Monthly | Yearly (optional)
notificationRules: []
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 · 297 lines · 106 tokens per session scan A 5d9c83ac1af5
manage-freeze-windows is a skill published in the GitHub repository harness/harness-ai (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 106 tokens to every session and 2,662 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to manage-freeze-windows, differing in 0 lines, and is treated as a copy.
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/.