A command that displays the current state of a PARA-based project workflow. PARA is a way of organizing information into Projects, Areas, Resources, and Archives.

Use it to inspect project context, list workflow files, check worktree health, review active plans, and see whether work should continue or be summarized.

It gives a quick view of active work, plans, summaries, branches, and worktrees. It can also reveal missing or outdated worktree references and suggest the next workflow action.

status — Skill by brian-lai

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 skills/brian-lai/para-programming-plugin/status

Any agent

npx skills add brian-lai/para-programming-plugin --skill status

Clone the repo

git clone --depth 1 https://github.com/brian-lai/para-programming-plugin

Made for: Claude Code, Codex.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 615 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.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.00615
Opus 5	$0.00006	$0.00308
Sonnet 5	$0.00002	$0.00123
Haiku 4.5	$0.00001	$0.00061

Measured 2d ago against content hash 46a60b31d8ae, 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.

skills/status/SKILL.md · 73 lines

How it starts

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

Display the current state of PARA context and workflow progress.

Usage

/para:status
/para:status --verbose         # Include file contents preview
/para:status --files           # List all context files

What It Does

Reads and parses context/context.md
Displays current work summary, active plans, and completed summaries
Shows worktree status (path, branch, existence)
Detects stale and orphaned worktrees
Detects workflow state and suggests next action

Output Format

PARA Status

Current Work:
   Implementing user authentication system

Active Plans:
   context/plans/2025-11-24-user-auth.md (created 2h ago)

Worktree:
   Path: .para-worktrees/user-auth
   Branch: para/user-auth
   Status: active (directory exists, branch valid)

Completed Summaries:
   context/summaries/2025-11-23-api-setup-summary.md

Last Updated: 2025-11-24T14:30:00Z

Next Action:
   Continue executing the plan, or run /para:summarize when complete

Worktree Health Checks

Active: worktree_path in metadata, directory exists, branch is valid
Stale reference: worktree_path in metadata but directory does not exist — warn: "Worktree referenced in context.md but directory missing. Run /para:execute to recreate or update context.md."
Orphaned worktree: Directory exists in .para-worktrees/ but is not referenced in context/context.md — warn: "Orphaned worktree found at .para-worktrees/{name}. Run git worktree remove to clean up or update context.md."
No worktree: No worktree_path in metadata — normal for idle/planning states or legacy --no-worktree execution

Implementation

Check if context/context.md exists
Parse the JSON block for active_context, completed_summaries, worktree_path, last_updated
Read the human-readable summary section
Check worktree state:
- If worktree_path is set, verify the directory exists
- List directories in .para-worktrees/ and compare against metadata references
Check git status for uncommitted changes
Determine workflow state and suggest next action:
- No context → /para:init
- Idle → /para:plan
- Planning → Review plan and begin execution
- Executing → Continue work or /para:summarize if done
- Summarized → /para:archive

Read the full file on GitHub · 73 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.

2d ago First seen · 73 lines · 12 tokens per session scan A 46a60b31d8ae

Subscribe to this mod's changes

status is a skill published in the GitHub repository brian-lai/para-programming-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 615 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.

Code review Git and workflow Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens