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/paulbreuler/limps/plan-check-statusgit clone --depth 1 https://github.com/paulbreuler/limpsWrote 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.
[](https://agentmods.dev/commands/paulbreuler/limps/plan-check-status)<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="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00828 |
| Opus 5 | $0.00000 | $0.00414 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
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 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.
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
- Shows status summary - Displays completed vs active agents
- Shows next task (if available) - Displays next best task
- Shows staleness report - Flags stale agents or plans
- 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:
-
Check plan status:
- If
--planprovided: Useget_plan_statusMCP tool (server:limps) to get status, thenget_next_taskMCP tool to get next task - Otherwise: Ask user which plan to check, or use
list_plansMCP tool to show available plans
- If
-
Check staleness:
- Use
check_stalenessMCP tool (server:limps) for the plan to identify stale agents or plans - Include staleness warnings in the output
- Use
-
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
-
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:
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 · 126 lines · 0 tokens per session scan A 5270a47c566a
plan-check-status is a command published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo 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.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
commit
智能生成 Git 提交信息并提交.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.
pm-board
Open the great-pm board — a native, zero-dependency project board (hybrid stage×status Kanban + artifact panels + verdict metrics) served from the great-pm plugin itself. Self-contained, no npm packages.
triage
../../templates/commands/triage.md.