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 agentmods add skills/loopdive/js2/shutdown-devnpx skills add loopdive/js2 --skill shutdown-devgit clone --depth 1 https://github.com/loopdive/js2What 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 | $0.00048 | $0.01355 |
| Opus 5 | $0.00024 | $0.00678 |
| Sonnet 5 | $0.00010 | $0.00271 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
shutdown-dev 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 yesterday.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shutdown Dev
Gracefully terminate a dev teammate's session while preserving their working context for future resumption.
When to use
- Team scale-down (e.g. going from 8 → 6 devs after OOM pressure or sprint close)
- Dev assigned to an orphaned branch after their PR was closed
- Sprint retrospective and wrap-up — shutting down devs between sprints
- Memory pressure requiring you to shed agent processes
Pre-shutdown checklist
-
Is the dev in the middle of something? Check their task status:
# via TaskList, filter for owner == <dev-name>If they're mid-implementation on a non-trivial task, prefer rotating them OFF that task first rather than losing the work.
-
Is the user currently talking to this dev? If yes, confirm with the user before shutting down.
-
Do they have uncommitted work in their worktree? Check via their file-locks entries and any in-flight PRs. Warn them to commit before approving shutdown.
Step 1: Send the shutdown_request
SendMessage to: <dev-name>
Type: shutdown_request
{"type": "shutdown_request", "reason": "<reason — e.g. 'Scaling team from 8 to 6 after OOM recovery; your current PR is merged/closed and you have no active task'>. Before approving shutdown: (1) write your working context to plan/agent-context/<dev-name>.md — include active branches, any in-progress thoughts, and anything a successor agent would need to resume. Keep it concise (~100 lines). (2) Commit any uncommitted WIP in your worktrees, or note explicitly that nothing is WIP. (3) Reply with shutdown_response approve=true. Your worktrees and branches stay — another dev can resume them later."}
Critical constraints in the message:
- MUST instruct them to write
plan/agent-context/<name>.mdFIRST - MUST tell them to commit uncommitted WIP
- MUST NOT ask them to narrate their context in the chat reply (that bloats the tech lead's context)
- Reply should be a one-line
shutdown_responseapprove=true
Step 2: Wait for response
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.
- yesterday First seen · 134 lines · 48 tokens per session scan A d49a51bb3684
shutdown-dev is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 1,355 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-08-30.
Other skills, from other repositories
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
babel-docs
Babel 7.x/8.x — plugins, presets, config, @babel/core, parser, traverse, types, CLI, preset-env.