claude-background-jobs
Skill0 starsChanged 57 days agoMITView on GitHub
Claude Code hook that denies background Bash commands that do not run through the run-job helper.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- instructions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- instructions/CLAUDE.mdCLAUDE.md
- author-skillSkill
- architectSkill
- arenaSkill
- astack-helpSkill
- astack-updateSkill
- brag-slimSkill
- bug-fixSkill
- claude-routerSkill
- codex-background-jobsSkill
- create-verification-skillSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- full-sendSkill
- grillingSkill
- handoffSkill
- harden-prSkill
- hillclimbSkill
- howSkill
- implementSkill
- improve-codebase-architectureSkill
- investigationSkill
- multi-phase-planSkill
- no-commentsSkill
- open-prSkill
- orchestrateSkill
- perf-issueSkill
- principlesSkill
- prototypeSkill
- refactoringSkill
- reflectSkill
- review-prSkill
- run-jobSkill
- ship-prSkill
- show-me-your-workSkill
- t3-previewSkill
- tddSkill
- teachSkill
- technical-writingSkill
- to-specSkill
- typescript-best-practicesSkill
- unslopSkill
- wayfinderSkill
- whySkill
- wizardSkill
- worktree-cleanupSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Put shell syntax and cd inside sh -c '...', and set variables with env VAR=value.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deny unbounded Claude Code background jobs
scripts/hook.py is a Claude Code PreToolUse hook for the Bash tool. It denies
a run_in_background call unless the command runs the helper from the
run-job skill, written literally:
python3 /absolute/path/to/run-job/scripts/run_job.py ARG ...python3can also bepython3.Nor an absolute path to either name.- The helper path must be the installed
run_job.py, written as an absolute path. - Each word is made of letters, digits,
_ . / : = @ % + , -, and single-quoted text. Any other character, such as$,~, a double quote, or a newline, denies the call.
Put shell syntax and cd inside sh -c '...', and set variables with
env VAR=value. The deny message gives the command forms for a finite job and a
long-lived process, with the helper's absolute path.
The hook checks only the command text. Shell functions and aliases in the user's shell setup, including zsh global aliases that expand inside arguments, can still change what runs.
The hook fails open. If the event is malformed, or the script or python3 is
missing, the hook exits with code 1. Claude Code reports the hook error and runs
the command.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

