agentmods.dev

status

A local diagnostic command for ClawdBod, a tool that records workouts and manages reminders to take breaks. It checks the tool's settings, workout log, user profile, and pause state.

In plain words
What is it for?
Checking local setup health, viewing how many workout sets were recorded, confirming whether break reminders are active, and identifying the relevant local data directory.
Why use it?
It shows whether ClawdBod is configured and running as expected, and points out missing settings, profiles, or workout records.

Command

5 2mo ago A scan 22 tokens original MIT
View the source file khur/clawdbod
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 commands/khur/clawdbod/status
Clone the repo
git clone --depth 1 https://github.com/khur/clawdbod
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00022 $0.00420
Opus 5 $0.00011 $0.00210
Sonnet 5 $0.00004 $0.00084
Haiku 4.5 $0.00002 $0.00042

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

Security

Grade A, and why

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

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.

commands/status.md · 43 lines

What it actually says

ClawdBod Status

Run a quick local diagnostic. No network involved — everything lives on this machine.

Steps

  1. Check config — read ~/.claude/clawdbod/config.json:

    • promptsBetweenBreaks and minMinutesBetweenBreaks (defaults 8 / 20 if missing)
    • Whether profile exists

  2. Check the workout log — with the Bash tool:

    wc -l < ~/.claude/clawdbod/workouts.jsonl 2>/dev/null || echo 0

  3. Check pause state — read state.json in the OS temp dir ($TMPDIR/clawdbod/state.json on macOS, /tmp/clawdbod/state.json on Linux). If pausedUntil is -1 → paused indefinitely; a future timestamp → paused until then; otherwise active.

  4. Display results:

ClawdBod Status

  Config:       ok (every 8 prompts, 20 min cooldown)
  Profile:      set
  Workout log:  84 sets recorded
  Breaks:       active
  Data:         ~/.claude/clawdbod/ (local only)

Everything looks good!

If something is off

  • No config file → "Using defaults (8 prompts / 20 min). Run /clawdbod:setup to customize."
  • No profile → "No profile set — add one with /clawdbod:config profile for calorie tracking."
  • Empty/missing log → "No workouts logged yet. They'll start recording automatically at your next break."
  • Paused → "Breaks are paused. Run /clawdbod:resume to get moving again."

Keep it concise — just the facts and action items.

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 · 43 lines · 22 tokens per session scan A f8e8917a79b8

Subscribe to this mod's changes

status is a command published in the GitHub repository khur/clawdbod (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 420 once invoked, about $0.0001 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-31.

claudeclaude-aiclaude-codeclaude-code-plugin
Related

Other commands, from other repositories

README

Git workflow and quality assurance commands for the claude-skills repository.

alirezarezvani/claude-skills · 0 tokens

convert-to-todowrite-tasklist-prompt

Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.

centminmod/my-claude-code-setup · 0 tokens

security-audit

Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.

centminmod/my-claude-code-setup · 0 tokens

statusbar-style

Switch the status-bar style (classic / capsule / hairline).

leeguooooo/claude-code-usage-bar · 13 tokens

hunt

Active vulnerability hunt against a target by invoking tools/hunt.py (which calls vulnscanner.sh against recon/ /). Auto-runs recon first if no recon dir exists. Usage: /hunt target.com.

Awarexone/Agentic-Bug-Hunter · 0 tokens

session-end

I'll summarize this coding session and update the memory system with our accomplishments.

brennercruvinel/CCPlugins · 0 tokens