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 commands/kesteva/soloflow/housekeepinggit clone --depth 1 https://github.com/kesteva/soloflowWhat 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.00037 | $0.00602 |
| Opus 5 | $0.00018 | $0.00301 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
housekeeping 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 3d 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.
What it actually says
/soloflow:housekeeping
Focused cruft sweep for .soloflow/ state. For the full review-queue triage (cruft + actions + visual + refinement), use /soloflow:review-queue.
$ARGUMENTS optionally includes one flag:
--dry-run— detect and print buckets only; no prompts, no writes.
If $ARGUMENTS is non-empty and not --dry-run, print usage and stop:
/soloflow:housekeeping [--dry-run]
Step 0 — Init
- If
.soloflow/does not exist, report: "SoloFlow not initialized. Run/soloflow:initfirst." and stop. - Initialize
cruft_resolved = 0.
Step 1 — Dry-run short-circuit
If $ARGUMENTS contains --dry-run:
- Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/state/cruft-detect.js". - If
total == 0, print"No cruft detected."and stop. - Otherwise, for each non-empty bucket, print the scenario name, the count, and a one-line summary per item (e.g.,
TASK-NNN — <short reason>). No prompts, no commits, no writes. - Stop.
Step 2 — Cleanup
Read docs/CRUFT-CLEANUP.md via the Read tool and follow its procedure to completion. Use housekeeping as the commit-message <command> label. The procedure updates the cruft_resolved counter initialized in Step 0.
Step 3 — Report
Print:
## Housekeeping — complete
Cruft resolved: {cruft_resolved}
If cruft_resolved == 0 and no cruft was detected, the one-line "No cruft detected." from Step 2 already stands; the final report can be a single line: Housekeeping — complete. Nothing to clean up.
Context Limit Self-Monitoring
This command runs in the main session. The context-monitor hook injects warnings when context usage is high.
When you receive a SOLOFLOW CONTEXT WARNING: finish the current per-item decision, then write a checkpoint.
When you receive a SOLOFLOW CONTEXT CRITICAL: finish the current decision, write a checkpoint, then use AskUserQuestion with options: Compact and continue / Save and exit.
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.
- 3d ago First seen · 60 lines · 37 tokens per session scan A 9cf7aa895f8e
housekeeping is a command published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 602 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.