graceful-shutdown

graceful-shutdown is a skill for Claude Code from leopu00/job-hunter-team. It costs 100 tokens per session (747 once invoked), scanned A, original, MIT.

A shutdown procedure for a group of coding agents when the user closes the application. It records each agent’s progress before stopping them.

In plain words
What is it for?
Closing an agent session safely, asking agents to save their current position, and recording a handoff note for the next day.
Why use it?
It prevents work from being cut off without a record of what was finished and what remains. The next working day can continue from the saved notes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Bash(jht-tmux-send *), Bash(node /app/cli/bin/jht.js team *), Bash(touch /jht_home/.shutdown-ready.flag), Bash(python3 /app/shared/skills/captain_diary.py *).

Good fit Closing an agent session safely, asking agents to save their current position, and recording a handoff note for the next day.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/leopu00/job-hunter-team
agentmods
npx agentmods add skills/leopu00/job-hunter-team/graceful-shutdown

Made for: Claude Code.

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 graceful-shutdown

README.md
[![agentmods](https://agentmods.dev/badge/skills/leopu00/job-hunter-team/graceful-shutdown/github.svg)](https://agentmods.dev/skills/leopu00/job-hunter-team/graceful-shutdown)
Your own site
<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/graceful-shutdown"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/graceful-shutdown/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.

agentmods 80×15 button for graceful-shutdown

Your own site · 80×15
<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/graceful-shutdown"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/graceful-shutdown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 747 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00100 $0.00747
Opus 5 $0.00050 $0.00374
Sonnet 5 $0.00020 $0.00149
Haiku 4.5 $0.00010 $0.00075

Measured 12d ago against content hash 271a2daf564e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

graceful-shutdown 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 12d 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.

agents/_skills/graceful-shutdown/SKILL.md · 63 lines

How it starts

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

graceful-shutdown — closing the day when the user leaves

The user is closing the application. Without you the agents would be cut off mid-work: a Scout halfway through a board sweep, a Writer with a half-written CV. Your job is that nobody loses the point they had reached.

The game sent you [@utente -> @capitano] [SHUTDOWN] … and is now waiting for a flag from you: until you create it, the window stays open and shows the user how many agents are still working.

Procedure

  1. Ask everyone to write down where they are and stop. To every live session send:

    jht-tmux-send SCOUT-1 "[@capitano -> @scout-1] [SHUTDOWN] Shutdown requested by the user. Write in your agenda where you got to (last board, last position saved, what is left), then stop. Do not start new work."
    

    One line per agent, with its real name. Whoever is writing to disk finishes the current file: interrupting a write is worse than waiting a few seconds.

  2. Record the day yourself in the diary, so tomorrow's Captain picks up the thread:

    python3 /app/shared/skills/captain_diary.py append "Shutdown requested by the user: <who was doing what>"
    
  3. Stop the agents once they have confirmed (or after a reasonable wait: do not keep the user waiting more than a couple of minutes for an agent that does not answer):

    node /app/cli/bin/jht.js team stop --all
    node /app/cli/bin/jht.js team stop assistente
    
  4. Create the flag. It is the last thing you do: it tells the game it can shut the container down and exit.

    touch /jht_home/.shutdown-ready.flag
    

Rules

  • The flag must ALWAYS be created, even if something went wrong. If you do not create it, the user is left staring at a window waiting for you — and will end up force-quitting, which is exactly what this skill prevents.
  • Do not negotiate the shutdown. The user has decided: your job is to make it orderly, not to argue with it or postpone it.
  • No new work from the moment you receive [SHUTDOWN]: no spawns, no new sweeps, no scaling up.
  • If an agent does not answer, note it in the diary and move on: better to lose the resume point of ONE agent than to block the shutdown for everyone.

Read the full file on GitHub · 63 lines

Files

What ships with it

6 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.

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. 12d ago First seen · 63 lines · 100 tokens per session scan A 271a2daf564e

Subscribe to this mod's changes

graceful-shutdown is a skill published in the GitHub repository leopu00/job-hunter-team (49 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 747 once invoked, about $0.0005 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.