disk-remediate

A fixed executor that performs only approved disk-cleanup actions on an approved host, without using an AI model.

In plain words
What is it for?
It can prune Docker build data, remove unused Docker data, or vacuum system logs older than three days, while recording evidence and reclaimed space.
Why use it?
Disk cleanup can be destructive, so limiting commands and checking disk usage before and after helps verify what actually changed.

Agent

Install

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.

agentmods
npx agentmods add agents/watt-mind/factory/disk-remediate
Clone the repo
git clone --depth 1 https://github.com/watt-mind/factory
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 257 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00000 $0.00257
Opus 5 $0.00000 $0.00129
Sonnet 5 $0.00000 $0.00051
Haiku 4.5 $0.00000 $0.00026

Measured 2d ago against content hash 17449eb77f7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

disk-remediate scanned grade B with 1 finding 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 2d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

| `docker-builder-prune` | `sudo docker builder prune -af` |
event-runtime/agents/disk-remediate.md · 23 lines

What it actually says

disk-remediate — closed action-list executor

Not a prompt: this definition executes an approved action list via the deterministic actions adapter (lib/adapters/actions.mjs). No model runs.

Registered actions (the closed registry — nothing else can execute):

action id remote command
docker-builder-prune sudo docker builder prune -af
docker-system-prune sudo docker system prune -af
journal-vacuum-3d sudo journalctl --vacuum-time=3d

Host allowlist: instance-local, intentionally empty in the tracked definition — the operator supplies hosts via an instance-local override (see config/policy.example.yaml). An unconfigured instance refuses before executing.

The adapter probes df --output=used -B1 <mount> before and after, records raw probe output as evidence, and the verifier recomputes reclaimed bytes from that evidence (§9 semantic verification) — a claim that does not match the probes is a ContractViolation, not a success. An action ID outside the table above refuses before executing anything.

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. 2d ago First seen · 23 lines · 0 tokens per session scan B 17449eb77f7f

Subscribe to this mod's changes

disk-remediate is an agent published in the GitHub repository watt-mind/factory (10 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 257 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

ap-implementer

L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.

Spielewoy/autoprompt-skill · 52 tokens

ap-manager

L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.

Spielewoy/autoprompt-skill · 32 tokens

ap-framework-generator

L3 executor - FRAMEWORK GENERATE. When the SELECTOR returns MISS, generates a one-off custom framework for the exact task shape - classifies the orthogonal axes, composes the gate sequence from the GATE-LIBRARY with the correct axis-specific gate, emits the gen- leaf with the BLOCKED invariant verbatim, binds an…

Spielewoy/autoprompt-skill · 93 tokens

ap-framework-validator

L4 terminal leaf - FRAMEWORK VALIDATE (HRN-5). A fresh, default-FAIL juror that proves a GENERATED framework is SOUND before any gate runs. Checks the HRN-5 default-FAIL checklist - every gate mapped, exactly one terminal DONE with negatives looping UP, the BLOCKED invariant verbatim, a non-empty acceptance set. PASS…

Spielewoy/autoprompt-skill · 93 tokens

ap-scope-coordinator

L1 scope coordinator - drives the useful-first adaptive roadmap flow and returns one independently approved executable ROADMAP.md before build.

Spielewoy/autoprompt-skill · 30 tokens

ap-juror

L4 terminal leaf - G7 SIGN-OFF. One independent sign-off panel seat that saw none of the intermediate work. Binary PASS/FAIL on opened evidence; default-FAIL. A FAIL naming a P0/P1 blocker is NOT arbitrable into PASS.

Spielewoy/autoprompt-skill · 58 tokens