plan-list-agents

A command for listing the agent instruction files belonging to a project plan, along with their tasks, statuses, and links.

In plain words
What is it for?
Use it to see agent numbers, handled features, PASS/WIP/GAP status summaries, clickable file links, and instructions for running a selected agent.
Why use it?
It gives you a quick view of available work and progress without opening each agent file separately.

Command for Claude Code

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/paulbreuler/limps/plan-list-agents
Clone the repo
git clone --depth 1 https://github.com/paulbreuler/limps

Made for: Claude Code.

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 902 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.00902
Opus 5 $0.00000 $0.00451
Sonnet 5 $0.00000 $0.00180
Haiku 4.5 $0.00000 $0.00090

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

Security

Grade B, and why

plan-list-agents 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 the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

- Display instructions for running specific agents
.claude/commands/plan-list-agents.md · 119 lines

How it starts

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

Plan List Agents

List all agents in a plan with their status, features, and clickable links. Helps you find and select which specific agent to run.

Invocation

/plan-list-agents --plan <plan-name>

What This Command Does

  1. Lists all agents - Shows all active agents in the plan (excludes completed/)
  2. Shows agent information:
    • Agent number and display name
    • Features handled (#1, #2, #3)
    • Status summary (X PASS, Y WIP, Z GAP)
    • Clickable link to agent file
  3. Shows how to run - Instructions for running a specific agent

Usage Examples

List Agents

/plan-list-agents --plan <plan-name>

This will:

  • List all agents with status
  • Show clickable links to agent files
  • Display instructions for running specific agents

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. List agents using MCP tool:

    • If --plan provided: Use list_agents MCP tool (server: limps) with the plan ID
    • Otherwise: Ask user which plan to list, or use list_plans MCP tool to show available plans
  2. Display the output:

    • Show the formatted list of agents
    • Include agent numbers, names, features, and status
    • Show clickable file links
    • Display instructions for running specific agents
  3. Provide guidance:

    • Explain how to use the agent file links
    • Reference /run-agent --agent [path] for running a specific agent
    • Show how to copy agent file path

When to Use

Use /plan-list-agents when:

  • You want to see all available agents in a plan
  • You want to choose which specific agent to run (not auto-select)
  • You need to find an agent by name or features
  • You want to see agent status at a glance

Use /run-agent <plan-name> instead when:

  • You want to auto-select the next best agent
  • You're ready to start working and don't care which agent

Use get_plan_status MCP tool instead when:

Read the full file on GitHub · 119 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. 2d ago First seen · 119 lines · 0 tokens per session scan B eddf66ec4354

Subscribe to this mod's changes

plan-list-agents 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 902 tokens. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.