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 JinNing6/Noosphere --skill windows-child-process-lifecyclegit clone --depth 1 https://github.com/JinNing6/NoosphereWrote 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/jinning6/noosphere/windows-child-process-lifecycle)<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/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/jinning6/noosphere/windows-child-process-lifecycle"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/windows-child-process-lifecycle.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.00075 | $0.00629 |
| Opus 5.5 | $0.00030 | $0.00252 |
| Sonnet 5.5 | $0.00015 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
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 1mo 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 — 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
- Use one foreground process for a single-writer workflow.
- Give the outer command a timeout longer than the expected child runtime. Prefer a yielded/waitable execution cell for long jobs.
- Store resumable checkpoints outside the authoritative output directory.
- Write authoritative outputs only after full validation; keep partial results in checkpoints.
- Bind checkpoints to code/config/freeze hashes so changed implementations cannot silently reuse stale rows.
After timeout, cancellation, or terminal loss
- Do not immediately relaunch.
- Query
Win32_Processby the distinctive command line and inspect PID, parent PID, creation time, CPU time, and working set. - Exclude the current diagnostic PowerShell process from matches.
- If a child remains, declare it the sole writer and monitor it read-only. Do not start another writer.
- Check progress through structural metadata only: checkpoint modification time, file size, unique successful identity count, and freeze hash. Avoid printing payloads or secrets.
- 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
- Detect authoritative-file writes that occurred after the parent command ended.
- Compare generation timestamps, history backups, freeze hashes, and outcome counts to identify concurrent overwrite.
- Reject mixed or stale checkpoints whose execution freeze differs from the current code/config freeze.
- 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.
- If concurrent writers touched the same latest view, discard that execution as clean-run evidence. Run once under a new freeze with one writer.
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.
- 1mo ago First seen · 51 lines · 75 tokens per session scan A e4eceaf89fb8
windows-child-process-lifecycle is a skill published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 4d ago), licensed Apache-2.0. It adds 75 tokens to every session and 629 once invoked, about $0.0003 per session on Opus 5.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
error-recovery
A guide to detecting and recovering from failures in long-running AI agents. It covers API outages, bad tool calls, broken conversation state, stalled streams, repeated loops, retries, fallback models, and circuit breakers that stop repeated failure.
pre-action-interceptors
Use when a tool error begins with "INTERCEPTOR:", a sent message was silently hedged or rewritten, or the user asks about active guards or blocked actions. Not for ordinary tool errors.
observability
Periodic health sweep of the running system via the debug pipeline (cloud logs / k8s / daemon / DB slices). On a real anomaly, open a bug task (--kind workitem) carrying the evidence refs so it re-enters the bugfix loop. A healthy sweep opens NO task — never fabricate a bug.
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
impact-trace
For a change point (function / type / endpoint / SQL column), enumerate its real blast radius across six dimensions with a grep citation per row, then derive the regression test scope. Every impact-table row must trace to a real search hit — never a self-asserted claim.
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.