limps: Command for Claude Code

.claude/commands/plan-check-status.md

plan-check-status is a command for Claude Code from paulbreuler/limps. It costs 0 tokens per session (828 once invoked), scanned A, original, MIT.

A command that gives a short status summary for a named plan. It can show completed and active agents, the next task, stale items, and links to plan files.

In plain words
What is it for?
Use it to review a plan's status, find the next task, spot outdated plans or agents, and open related files.
Why use it?
It lets you check progress quickly without opening several plan files or reading a long report.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is paulbreuler/limps's own configuration. It tells Claude Code how to work on limps itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything limps configures →

Reuse

Borrowing it

Nothing to install: this file belongs to paulbreuler/limps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/paulbreuler/limps/main/.claude/commands/plan-check-status.md
Clone the repo
git clone --depth 1 https://github.com/paulbreuler/limps

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plan-check-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/paulbreuler/limps/plan-check-status/github.svg)](https://agentmods.dev/commands/paulbreuler/limps/plan-check-status)
Your own site
<a href="https://agentmods.dev/commands/paulbreuler/limps/plan-check-status"><img src="https://agentmods.dev/badge/commands/paulbreuler/limps/plan-check-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plan-check-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/paulbreuler/limps/plan-check-status"><img src="https://agentmods.dev/badge/commands/paulbreuler/limps/plan-check-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 828 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00828
Opus 5.5 $0.00000 $0.00331
Sonnet 5.5 $0.00000 $0.00166
Haiku 4.5 $0.00000 $0.00083

Measured 1mo ago against content hash 5270a47c566a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-check-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 1mo 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.

.claude/commands/plan-check-status.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan Check Status

Simple entry point: "I want to check plan status". Shows plan status without overwhelming detail.

Invocation

/plan-check-status
/plan-check-status --plan <plan-name>

What This Command Does

  1. Shows status summary - Displays completed vs active agents
  2. Shows next task (if available) - Displays next best task
  3. Shows staleness report - Flags stale agents or plans
  4. Shows quick links - Provides links to plan files

Usage Examples

Check Status

/plan-check-status --plan <plan-name>

This will:

  • Show status summary
  • Show next task if available
  • Show staleness warnings
  • Display quick links

If no plan is specified, use list_plans MCP tool to see available plans first.

Instructions for Claude

When this command is invoked, you must:

  1. Check plan status:

    • If --plan provided: Use get_plan_status MCP tool (server: limps) to get status, then get_next_task MCP tool to get next task
    • Otherwise: Ask user which plan to check, or use list_plans MCP tool to show available plans
  2. Check staleness:

    • Use check_staleness MCP tool (server: limps) for the plan to identify stale agents or plans
    • Include staleness warnings in the output
  3. Display the output:

    • Show QUICK DECISION section
    • Show PLAN STATUS section (from get_plan_status)
    • Show STALENESS WARNINGS section (if any, from check_staleness)
    • Show RECOMMENDED ACTIONS section
    • Display quick links
  4. Provide guidance:

    • Explain what the status means
    • Suggest next actions based on status
    • Reference related commands

When to Use

Use /plan-check-status when:

  • You want to see plan status quickly
  • You need a status overview without full details
  • You want to check progress

Use get_next_task MCP tool instead when:

  • You want to get the next best task with scoring breakdown
  • You need detailed task recommendations

Use get_plan_status MCP tool instead when:

Read the full file on GitHub · 126 lines

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. 1mo ago First seen · 126 lines · 0 tokens per session scan A 5270a47c566a

Subscribe to this mod's changes

plan-check-status is a command published in the GitHub repository paulbreuler/limps (10 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 828 tokens. 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.