monitoring-post-release

monitoring-post-release is a skill for Claude Code from Nolane-x/forge-os. It costs 32 tokens per session (177 once invoked), scanned A, original, MIT.

An operations skill for checking a software release after it goes live.

In plain words
What is it for?
Use it to monitor a release after deployment and assess whether the planned post-release conditions are being met.
Why use it?
It gives post-release decisions a defined scope and ties them to evidence instead of relying on unbounded judgment.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the forgeos plugin — 196 skills, 1 command, 1 agent, 1 MCP server shipped together

Good fit Use it to monitor a release after deployment and assess whether the planned post-release conditions are being met.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nolane-x/forge-os/monitoring-post-release
Install

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.

Any agent
npx skills add Nolane-x/forge-os --skill monitoring-post-release
Clone the repo
git clone --depth 1 https://github.com/Nolane-x/forge-os

Made for: Claude Code.

Or install forgeos, the plugin that ships this one along with the rest of its 196 skills, 1 command, 1 agent, 1 MCP server.

Wrote 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.

agentmods badge for monitoring-post-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/nolane-x/forge-os/monitoring-post-release/github.svg)](https://agentmods.dev/skills/nolane-x/forge-os/monitoring-post-release)
Your own site
<a href="https://agentmods.dev/skills/nolane-x/forge-os/monitoring-post-release"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/monitoring-post-release/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.

agentmods 80×15 button for monitoring-post-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/nolane-x/forge-os/monitoring-post-release"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/monitoring-post-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 177 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00177
Opus 5 $0.00016 $0.00088
Sonnet 5 $0.00006 $0.00035
Haiku 4.5 $0.00003 $0.00018

Measured 5d ago against content hash 6bc44e6210c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

monitoring-post-release 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 5d 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.

skills-v2/l1/operations/monitoring-post-release/SKILL.md · 23 lines

What it actually says

Monitoring Post Release

Core principle

Monitoring post release within operations lifecycle boundaries. Deterministic checks own scope, typed preconditions, evidence, and coverage; the agent performs only the domain judgment that cannot be encoded safely.

Do not activate when

  • the requested outcome does not require monitoring post release within operations lifecycle boundaries
  • the typed inputs for monitoring-post-release are absent and another technique owns the outcome
Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 5d ago First seen · 23 lines · 32 tokens per session scan A 6bc44e6210c8

Subscribe to this mod's changes

monitoring-post-release is a skill published in the GitHub repository Nolane-x/forge-os (10 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 177 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories