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.
git clone --depth 1 https://github.com/skyfox675/agents-skillsWrote 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/commands/skyfox675/agents-skills/kill)<a href="https://agentmods.dev/commands/skyfox675/agents-skills/kill"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/kill/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/commands/skyfox675/agents-skills/kill"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/kill.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.00065 | $0.00954 |
| Opus 5.5 | $0.00026 | $0.00382 |
| Sonnet 5.5 | $0.00013 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
kill 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/kill — emergency agent load-shedding
Arguments: $ARGUMENTS — empty means stabilize automatically (kill newest-first until pressure recovers); a number kills exactly that many newest agents; all stops every running sub-agent. This is an emergency command: act immediately, measure, report after — do not ask for confirmation mid-incident.
Why newest-first (LIFO): the newest agents have invested the least work; the oldest are closest to a push or PR. Killing newest-first sheds the same load while destroying the least progress — and killed agents' worktrees survive, so their work is salvageable either way (see step 5).
Steps
-
Measure once, fast. Memory pressure (
memory_pressureon macOS — read the percentage and state;vm_statfor compressor/swap activity; on Linux,free -m+/proc/pressure/memory), load average (uptime), and the top memory consumers (ps aux | sort -rk4— look for agent-spawned trees: test runners like vitest/playwright/jest workers, bundlers, language servers spawned under worktree paths). One snapshot is enough — the situation is degrading while you measure. -
Stop new spending immediately. No new dispatches, no new pushes (each push may fan out a pre-push hook test suite — that is usually the very load source). If an orchestration loop is running, hold all free slots (see orchestrating-slots backpressure).
-
Kill newest-first, in waves. List running sub-agents (TaskList / your harness's running-task view), order by start time descending:
- Stop the newest agent via the harness (TaskStop or equivalent) — graceful, the harness records the kill.
- Then sweep its orphans: hook-spawned processes (test runners, watchers) under that agent's worktree path that survived the parent —
kill(TERM) the process group first, escalate to-9only for survivors after a few seconds. - Wave size: 1–2 agents, then re-measure (step 4). With an explicit count or
all, do the whole batch in one wave. - Never touch: your own session's process tree, other operators' processes, anything not descended from an agent you started. When in doubt about a process's owner, leave it — a missed orphan costs memory; killing the wrong tree costs someone else's work.
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 · 30 lines · 65 tokens per session scan A b75f1c6adb92
kill is a command published in the GitHub repository skyfox675/agents-skills (11 stars, last pushed 11d ago), licensed MIT. It adds 65 tokens to every session and 954 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.