Run any Skill in Manus with one click

janitor-global-disarm

Stars1

Forks1

UpdatedJune 30, 2026 at 14:06

TRUE machine-wide STOP of the global ai-maestro-janitor daemon AND every per-session heartbeat. Sets the kill-switch so the daemon exits and removes its OS keepalive, AND raises the global-pause flag so every armed session's heartbeat self-disarms (deletes its own cron) on its next fire — halting all janitor activity across ALL projects and instances, not just the daemon. The also-stop-the-daemon sibling of /janitor-global-pause (which keeps the daemon alive). Trigger with /janitor-global-disarm, "stop all janitors", "globally disarm the janitor", "halt the janitor daemon everywhere".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Emasoft

Emasoft/ai-maestro-janitor

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name

janitor-global-disarm

description

Janitor global disarm (machine-wide TRUE stop)

Overview

TRUE machine-wide stop of the global janitor daemon by setting the kill-switch. This is the teardown stop — distinct from /janitor-global-pause (which only idles the daemon) and from /janitor-disarm (which removes only THIS project's heartbeat cron). It stops the singleton daemon that serves ALL projects:

the running daemon sees the kill-switch on its next loop and exits gracefully;
if the OS keepalive (LaunchAgent / systemd unit) is installed, the daemon removes it on the way out, so launchd/systemd cannot resurrect it;
per-session heartbeats stop lazy-spawning a new daemon (ensure_daemon_running honors the kill-switch), so the stop holds;
every armed session's heartbeat SELF-DISARMS — disarm also raises the global-pause flag, which dispatch.py honors at Phase 0: on the next fire it emits a bare [janitor-self-disarm] marker so the session runs /janitor-disarm and deletes its own cron (TRDD-RQ9FIFX6, superseding the silence-only behavior of TRDD-NJ22HNC3). This is a TRUE stop, not a silence — a cron FIRE is a full Claude turn that re-reads the whole session context (~618k cached tokens, billed at the 0.1× cache-read rate, not free) whether or not detectors run, so only deleting the cron makes a fire cost zero. Rollout caveat: the marker is baked into the cron prompt at arm time, so crons armed BEFORE this shipped won't self-disarm on their own — run /janitor-disarm once in each such session.

To revive: run /janitor-global-arm (clears the kill-switch; re-arm a session with /janitor-arm and its next heartbeat spawns a fresh daemon). For a temporary stop that keeps the daemon alive use /janitor-global-pause instead.

When NOT to use

A temporary stop machine-wide that keeps the daemon alive → /janitor-global-pause (the daemon resumes instantly; sessions re-arm to restart their heartbeats).
Silence only THIS project's heartbeat → /janitor-disarm (local).
Uninstall the plugin entirely → Claude Code's plugin uninstall flow.

Instructions

Set the kill-switch via the backing CLI (single source of truth for the flag path — never write the flag file by hand):
```
uv run --script --quiet "${CLAUDE_PLUGIN_ROOT}/scripts/global_control_cli.py" disarm "via /janitor-global-disarm"
```
Report the one-line result the CLI prints. The daemon may take up to its loop interval (≤ 60 s) to notice the flag and exit; that is expected.

Output

One line confirming the janitor is disarmed machine-wide, with the reminder that /janitor-global-arm revives it. No teardown beyond the kill-switch flag is written here — the daemon performs its own shutdown + keepalive removal.

Error Handling

${CLAUDE_PLUGIN_ROOT} unset → abort "plugin not installed".
The CLI never blocks; it writes the flag atomically and returns immediately.
If the daemon was not running, the flag is still set (harmless) so a future lazy-spawn is suppressed until /janitor-global-arm clears it.

Examples

User: /janitor-global-disarm
User: stop all janitors everywhere
User: globally disarm the janitor daemon

Scope

ONLY sets the two machine-wide flags via the backing CLI — the kill-switch (daemon exits) AND the global-pause flag (each armed session's heartbeat self-disarms — deletes its own cron — on its next fire, TRDD-RQ9FIFX6). The skill does not itself remove a cron, uninstall the plugin, or delete state; the daemon's own shutdown path removes the OS keepalive. This skill just trips the switches.

Resources

${CLAUDE_PLUGIN_ROOT}/scripts/global_control_cli.py — backing CLI (disarm/arm/pause/unpause/status).
/janitor-global-arm — clears the kill-switch and revives the daemon.
/janitor-global-pause — the lighter machine-wide suspend (daemon idles, no teardown).
/janitor-disarm — the narrower per-project heartbeat stop.

More from this repository

same repository

janitor-memory-consolidate

Emasoft/ai-maestro-janitor

CONSOLIDATE (MERGE) executor — fuses two duplicate memory notes about the SAME subject + same type into one page (dedup lessons, redirect backlinks, keep the oldest origin date), through the crash-safe transaction core, never editing a live page. ABSTAINS on uncertainty, cross-type/cross-scope/two-hub, or a third page sharing the subject. Use on a [janitor-memory-consolidate] marker, or "consolidate / merge / deduplicate the memory", "two notes cover the same thing", "fold these memory pages together".

2026-07-261

janitor-memory-recall

Emasoft/ai-maestro-janitor

RECALL — before working on a file or debugging/deciding, surface the right memory WIKI page and navigate it. Two entry points - FILE-anchored (about to edit a file → surface that functionality's HUB page and descend its links to the detail needed) and SYMPTOM ("have we hit this before?" → rank pages by how the symptom hits their description/title/tags). Use before re-deriving architecture/gotchas, or when the user says "recall memories about X" or "did we already solve this". Reads only the pages the task needs, degrading to grep when memgrep is absent. The RECALL leg of the wiki-memory protocol.

2026-07-261

janitor-memory-write

Emasoft/ai-maestro-janitor

MEMORIZE — capture a durable decision/fact into the project's memory WIKI as a navigable page, not a loose note. Use after a bug-autopsy gotcha, a design/architecture decision, a project constraint not derivable from code, a confirmed user preference, or when the user says "remember this", "memorize this", "save a memory". Finds the right existing wikimem page first so it never duplicates; only when none fits, creates a HUB / ASPECT / COMPONENT page via the expand/reduce decision, wires it into the See-also web, and indexes it by symptom. The MEMORIZE leg of the wiki-memory protocol.

2026-07-261

janitor-memory-update

Emasoft/ai-maestro-janitor

UPDATE — modify an existing memory WIKI page when something changes — ADD a decision to the page that owns the subject, CORRECT a memory a new discovery contradicts (the 2-step non-destructive protocol), or RESHAPE a page that outgrew its tier (expand a shared rule into an aspect, reduce element-specific detail into its component page). Use when a decision changes, a memory turns out wrong, a page mixes too many subjects, or the user says "update the memory", "that's no longer true", "fix the note about Y", "this memory is outdated". Keeps the See-also web, the hub map, and the lessons trail consistent. The UPDATE leg of the wiki-memory protocol.

2026-07-261

janitor-auto-manage-oauth-on

Emasoft/ai-maestro-janitor

Opts THIS machine into the janitor's unattended multi-account OAuth rotator. Sets an opt-in flag the always-on janitor daemon's 60s oauth-rotator-tick Task reads to rotate the live Claude Code credential to an alternate paid account before a rate-limit 429 stalls an overnight session. Default OFF, macOS only, idempotent; refuses if a pinning env var would defeat rotation. Trigger with /janitor-auto-manage-oauth-on, "turn on oauth rotation", or "enable account rotator".

2026-07-261

janitor-token-attribution

Emasoft/ai-maestro-janitor

Rank every project on this machine by how many tokens it is burning right now and name the one to throttle — the fleet token-attribution dashboard. The account 5h/7d utilization% is aggregate across all your parallel projects; this scans each project's transcripts to say WHICH one is over-consuming (large 5h share AND above its own baseline) and where its spike came from. Read-only. Use when the user asks which project is eating the token budget / which session to throttle / who is burning the rate-limit window.

2026-07-261

name

janitor-global-disarm

description

Janitor global disarm (machine-wide TRUE stop)

Overview

the running daemon sees the kill-switch on its next loop and exits gracefully;
if the OS keepalive (LaunchAgent / systemd unit) is installed, the daemon removes it on the way out, so launchd/systemd cannot resurrect it;
per-session heartbeats stop lazy-spawning a new daemon (ensure_daemon_running honors the kill-switch), so the stop holds;
every armed session's heartbeat SELF-DISARMS — disarm also raises the global-pause flag, which dispatch.py honors at Phase 0: on the next fire it emits a bare [janitor-self-disarm] marker so the session runs /janitor-disarm and deletes its own cron (TRDD-RQ9FIFX6, superseding the silence-only behavior of TRDD-NJ22HNC3). This is a TRUE stop, not a silence — a cron FIRE is a full Claude turn that re-reads the whole session context (~618k cached tokens, billed at the 0.1× cache-read rate, not free) whether or not detectors run, so only deleting the cron makes a fire cost zero. Rollout caveat: the marker is baked into the cron prompt at arm time, so crons armed BEFORE this shipped won't self-disarm on their own — run /janitor-disarm once in each such session.

When NOT to use

A temporary stop machine-wide that keeps the daemon alive → /janitor-global-pause (the daemon resumes instantly; sessions re-arm to restart their heartbeats).
Silence only THIS project's heartbeat → /janitor-disarm (local).
Uninstall the plugin entirely → Claude Code's plugin uninstall flow.

Instructions

Set the kill-switch via the backing CLI (single source of truth for the flag path — never write the flag file by hand):
```
uv run --script --quiet "${CLAUDE_PLUGIN_ROOT}/scripts/global_control_cli.py" disarm "via /janitor-global-disarm"
```
Report the one-line result the CLI prints. The daemon may take up to its loop interval (≤ 60 s) to notice the flag and exit; that is expected.

Output

Error Handling

${CLAUDE_PLUGIN_ROOT} unset → abort "plugin not installed".
The CLI never blocks; it writes the flag atomically and returns immediately.
If the daemon was not running, the flag is still set (harmless) so a future lazy-spawn is suppressed until /janitor-global-arm clears it.

Examples

User: /janitor-global-disarm
User: stop all janitors everywhere
User: globally disarm the janitor daemon

Scope

Resources

${CLAUDE_PLUGIN_ROOT}/scripts/global_control_cli.py — backing CLI (disarm/arm/pause/unpause/status).
/janitor-global-arm — clears the kill-switch and revives the daemon.
/janitor-global-pause — the lighter machine-wide suspend (daemon idles, no teardown).
/janitor-disarm — the narrower per-project heartbeat stop.