para-status

para-status is a command for Claude Code from aroyburman-codes/para-second-brain. It costs 0 tokens per session (718 once invoked), scanned A, original, MIT.

A command that reports the state of a PARA folder system by counting items, reading their status, and flagging work that needs attention. PARA organizes information into Projects, Areas, Resources, and Archive.

In plain words
What is it for?
Use it to view all four categories or inspect one category, including project phases and health, resource review dates, and attention flags.
Why use it?
It saves you from opening many folders and context files to understand what is active, healthy, overdue for review, or at risk.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the para-second-brain plugin — 1 skill, 5 commands shipped together

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/aroyburman-codes/para-second-brain/para-status
Clone the repo
git clone --depth 1 https://github.com/aroyburman-codes/para-second-brain

Made for: Claude Code.

Or install para-second-brain, the plugin that ships this one along with the rest of its 1 skill, 5 commands.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/aroyburman-codes/para-second-brain/para-status.svg)](https://agentmods.dev/commands/aroyburman-codes/para-second-brain/para-status)
Your own site
<a href="https://agentmods.dev/commands/aroyburman-codes/para-second-brain/para-status"><img src="https://agentmods.dev/badge/commands/aroyburman-codes/para-second-brain/para-status.svg" alt="Measured on agentmods" 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 718 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.1 $0.00000 $0.00718
Opus 5 $0.00000 $0.00359
Sonnet 5 $0.00000 $0.00144
Haiku 4.5 $0.00000 $0.00072

Measured 6d ago against content hash 6f6cd04f7fa2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

para-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 6d 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/para-status.md · 89 lines

How it starts

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

/para-status

Show an overview of your PARA system — item counts, statuses, and attention-needed flags.

Usage

/para-status [category]
  • No argument: Show overview of all categories
  • projects, areas, resources, or archive: Show details for that category only

Steps

Find the PARA Root

Look for .para-config.json in:

  • Current working directory
  • ~/para/
  • Walk up from current directory

If not found, tell the user to run /para-setup first.

Overview Mode (no category specified)

  1. Scan all categories. For each of Projects, Areas, Resources, Archive:

    • Count the number of items (directories containing context.md)
    • Read each item's context.md to extract status info
  2. Build the overview table:

    PARA System Overview ({PARA_ROOT})
    ══════════════════════════════════
    
    📂 Projects: {count} active
      • {name} — {phase}, {health}
      • {name} — {phase}, {health}
    
    📂 Areas: {count} active
      • {name} — {health}
      • {name} — {health}
    
    📂 Resources: {count} items
      • {name} — last reviewed {date}
      • {name} — last reviewed {date}
    
    📦 Archive: {count} items
    
  3. Add attention flags at the bottom:

    • ⚠️ Projects at risk or off track
    • ⚠️ Areas marked "Needs Attention" or "Neglected"
    • ⚠️ Resources not reviewed in 3+ months
    • ⚠️ More than 10 active projects (overcommitted)
    • ⚠️ Items with empty or minimal context.md

Category Detail Mode

When a specific category is provided:

  1. List all items in that category with full status details
  2. For Projects: Show phase, health, target date, milestone progress (count of checked vs total checkboxes)
  3. For Areas: Show health, standards count, cadence items
  4. For Resources: Show tags, last reviewed date, source count
  5. For Archive: Show item names and which original category they came from (if detectable from context.md)

Reading Status from context.md

Extract status by reading context.md and parsing:

  • Phase: Look for **Phase:** line
  • Health: Look for **Health:** line
  • Target Date: Look for **Target Date:** line
  • Last Updated: Look for **Last Updated:** line
  • Last Reviewed: Look for ## Last Reviewed section (Resources)
  • Tags: Look for ## Tags section (Resources)

Read the full file on GitHub · 89 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. 6d ago First seen · 89 lines · 0 tokens per session scan A 6f6cd04f7fa2

Subscribe to this mod's changes

para-status is a command published in the GitHub repository aroyburman-codes/para-second-brain (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 718 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.