windows-child-process-lifecycle

windows-child-process-lifecycle is a skill for Claude Code, Codex from JinNing6/Noosphere. It costs 75 tokens per session (629 once invoked), scanned A, original, Apache-2.0.

A Windows process-management guide for long-running scripts, builds, benchmarks, models, or tests started by PowerShell. It focuses on the full child-process tree rather than only the parent shell.

In plain words
What is it for?
Use it to launch single-writer jobs, inspect surviving child processes, monitor checkpoints safely, and publish output only after complete validation.
Why use it?
It helps prevent orphaned processes, competing writers, and corrupted output after a timeout, cancelled command, or closed terminal.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

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.

agentmods
npx agentmods add skills/jinning6/noosphere/windows-child-process-lifecycle
Any agent
npx skills add JinNing6/Noosphere --skill windows-child-process-lifecycle
Clone the repo
git clone --depth 1 https://github.com/JinNing6/Noosphere

Made for: Claude Code, Codex.

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 windows-child-process-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/jinning6/noosphere/windows-child-process-lifecycle.svg)](https://agentmods.dev/skills/jinning6/noosphere/windows-child-process-lifecycle)
Your own site
<a href="https://agentmods.dev/skills/jinning6/noosphere/windows-child-process-lifecycle"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/windows-child-process-lifecycle.svg" alt="Measured on agentmods" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 629 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00075 $0.00629
Opus 5 $0.00037 $0.00315
Sonnet 5 $0.00015 $0.00126
Haiku 4.5 $0.00007 $0.00063

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

Security

Grade A, and why

windows-child-process-lifecycle 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 6d 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.

shared_skills/active/windows-child-process-lifecycle/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Windows Child Process Lifecycle

Treat the actual child process tree, not the parent shell result, as the lifecycle authority.

Before launch

  1. Use one foreground process for a single-writer workflow.
  2. Give the outer command a timeout longer than the expected child runtime. Prefer a yielded/waitable execution cell for long jobs.
  3. Store resumable checkpoints outside the authoritative output directory.
  4. Write authoritative outputs only after full validation; keep partial results in checkpoints.
  5. Bind checkpoints to code/config/freeze hashes so changed implementations cannot silently reuse stale rows.

After timeout, cancellation, or terminal loss

  1. Do not immediately relaunch.
  2. Query Win32_Process by the distinctive command line and inspect PID, parent PID, creation time, CPU time, and working set.
  3. Exclude the current diagnostic PowerShell process from matches.
  4. If a child remains, declare it the sole writer and monitor it read-only. Do not start another writer.
  5. Check progress through structural metadata only: checkpoint modification time, file size, unique successful identity count, and freeze hash. Avoid printing payloads or secrets.
  6. Let a healthy child finish naturally when safe. If termination is necessary, terminate the verified child process tree and confirm every descendant is gone before relaunching.

Recovery and integrity

  1. Detect authoritative-file writes that occurred after the parent command ended.
  2. Compare generation timestamps, history backups, freeze hashes, and outcome counts to identify concurrent overwrite.
  3. Reject mixed or stale checkpoints whose execution freeze differs from the current code/config freeze.
  4. For append-only retry logs, freeze the first successful record per identity. Do not let later stochastic retries replace an established success unless the protocol explicitly pre-registers another rule.
  5. If concurrent writers touched the same latest view, discard that execution as clean-run evidence. Run once under a new freeze with one writer.

Read the full file on GitHub · 51 lines

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. 6d ago First seen · 51 lines · 75 tokens per session scan A e4eceaf89fb8

Subscribe to this mod's changes

windows-child-process-lifecycle is a skill published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 6d ago), licensed Apache-2.0. It adds 75 tokens to every session and 629 once invoked, about $0.0004 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.