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 The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill test-orphan-guardgit clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/test-orphan-guard)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/test-orphan-guard"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/test-orphan-guard/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/test-orphan-guard"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/test-orphan-guard.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.00207 | $0.02264 |
| Opus 5.5 | $0.00083 | $0.00906 |
| Sonnet 5.5 | $0.00041 | $0.00453 |
| Haiku 4.5 | $0.00021 | $0.00226 |
Grade B, and why
test-orphan-guard scanned grade B 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 10d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
into `~/.claude/settings.json` (the `update-config` skill can do this). How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-orphan-guard
Node's test runner leaks processes. This skill stops the leak at the source and cleans up what already leaked.
Why this happens (read this first — it tells you what's safe to kill)
node --test --test-isolation=process runs each test file in its own child
node process. Those children are supposed to die when the run ends. Two
things break that:
- The runner dies without reaping its children. If the top-level
node --testis killed (Ctrl-C, a timeout in the harness, an OOM, a crashed wrapper), its child test processes get reparented to PID 1 (launchd on macOS). They are now orphans: no parent will everwait()on them or shut them down. - A test has no timeout. Fixtures run with
--test-timeout=0never self-terminate. Combined with orphaning, a single hung test file can spin a full CPU core forever — and they stack up. Fifteen of them at ~35% CPU each is 5–6 cores pinned and a machine that's audibly struggling.
So the leaked processes are not "doing nothing" — they're usually busy-looping at high CPU. The signatures that mark a process as safe to kill:
- Orphan — its
PPIDis1. Its runner is gone; it is definitionally a leftover. This is the strongest and most common signal. - Runaway — its command line is a
node --testprocess pinned at high CPU for minutes. A healthy test file finishes in seconds; one pinned for 3+ minutes is hung.
Everything else that happens to be a node process — MCP servers (memtrace,
github, context7, xcodebuild), editor/Codex helpers, node_repl, LM Studio —
must never be touched. None of those carry --test on their command line,
which is the primary safety boundary the tools use.
The two tools
This skill ships a prevention tool and a cure tool. They cover each other: prevention stops same-process-group children from leaking; cure mops up anything that still escapes (or already leaked before the skill was in place).
What ships with it
5 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.
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.
- 10d ago First seen · 192 lines · 207 tokens per session scan B 18f9bb2772a8
test-orphan-guard is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed today), licensed MIT. It adds 207 tokens to every session and 2,264 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.
Other skills, from other repositories
run-checks
Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests"…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
agent-qa-debug-fix
Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.
debug-failing-test
Debug a failing test using an iterative logging approach, then clean up and document the learning.
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
health
Audits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.