project-status

project-status is a command for Claude Code from bijutharakan/multi-agent-squad. It costs 20 tokens per session (1,076 once invoked), scanned A, original, MIT.

A command that produces a status report for active project features, worktrees, agents, and GitHub issues. A worktree is a separate working copy of a Git repository, and an agent is an assigned automated worker.

In plain words
What is it for?
Use it to review the current state of multi-agent development, including feature progress, worktree status, linked issues and pull requests, blockers, and completed work.
Why use it?
Work spread across repositories and agents can be difficult to track in separate places. This gathers progress, blockers, assignments, and recent completions into one view.

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/bijutharakan/multi-agent-squad/project-status
Clone the repo
git clone --depth 1 https://github.com/bijutharakan/multi-agent-squad

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/bijutharakan/multi-agent-squad/project-status.svg)](https://agentmods.dev/commands/bijutharakan/multi-agent-squad/project-status)
Your own site
<a href="https://agentmods.dev/commands/bijutharakan/multi-agent-squad/project-status"><img src="https://agentmods.dev/badge/commands/bijutharakan/multi-agent-squad/project-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,076 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 $0.00020 $0.01076
Opus 5 $0.00010 $0.00538
Sonnet 5 $0.00004 $0.00215
Haiku 4.5 $0.00002 $0.00108

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

Security

Grade A, and why

project-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 4d 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/project-status.md · 162 lines

How it starts

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

Project Status Command

Get a complete overview of your project's current state across all repositories and active features.

What This Command Shows

  1. Active Features - All features in development
  2. Worktree Status - State of each worktree
  3. Agent Assignments - Who's working on what
  4. GitHub Issues - Linked issues and PRs
  5. Blockers - What's holding up progress
  6. Recent Completions - What was finished recently

Usage

  • /project-status
  • "Show me the project status"
  • "What's the current state?"
  • "Status report"

Status Report Format

# Multi-Agent Squad Status Report
Generated: 2024-01-20 14:30 UTC

## 📊 Overview
- Active Features: 3
- Active Worktrees: 7
- Assigned Agents: 5
- Open PRs: 2
- Blocked Items: 1

## 🚀 Active Features

### Feature: user-authentication
**GitHub Issue**: #47 (In Progress)
**Priority**: High
**Started**: 2 days ago

**Worktrees**:
- ✅ backend/feature-user-authentication (90% complete)
  - 15 commits ahead
  - Last commit: "Add JWT token validation"
  - Assigned: Backend Developer Agent
  
- 🔄 frontend/feature-user-authentication (60% complete)
  - 8 commits ahead
  - Last commit: "Implement login form"
  - Assigned: Frontend Developer Agent
  
- 🔄 mobile/feature-user-authentication (40% complete)
  - 5 commits ahead
  - Last commit: "Add biometric auth"
  - Assigned: Mobile Developer Agent

**Next Steps**: Frontend needs to integrate with backend API

### Feature: payment-integration
**GitHub Issue**: #48 (In Progress)
**Priority**: High
**Started**: Today

**Worktrees**:
- 🔄 backend/feature-payment-integration (20% complete)
  - 3 commits ahead
  - Assigned: Backend Developer Agent
  
**Blockers**: ⚠️ Waiting for Stripe API credentials

## 🔍 Pull Requests

### Open PRs
1. **#152** - feat: Add user authentication (backend)
   - Status: In Review
   - Reviewers: @senior-engineer
   - Checks: ✅ All passing

2. **#153** - feat: Login UI components
   - Status: Draft
   - Reviewers: Not assigned yet
   - Checks: 🔄 Running

## ⚠️ Blockers & Issues

1. **Payment Integration** - Missing Stripe API credentials
   - Impact: Backend development blocked
   - Action: Contact DevOps for credentials
   - Assigned: @orchestrator

## ✅ Recently Completed

- **Feature: search-optimization** (Completed yesterday)
  - Merged PRs: #149, #150, #151
  - Issue #45 closed
  
- **Bug: memory-leak-fix** (Completed 2 days ago)
  - Merged PR: #148
  - Issue #44 closed

## 👥 Agent Activity

| Agent | Current Task | Status |
|-------|-------------|--------|
| Backend Developer | Payment API endpoints | Active |
| Frontend Developer | Auth UI polish | Active |
| Mobile Developer | Biometric integration | Active |
| QA Engineer | Testing auth flows | Scheduled |
| DevOps Engineer | Setting up Stripe | Requested |

## 📈 Velocity Metrics

- Features completed this week: 2
- Average feature cycle time: 4.5 days
- PR review time: 6 hours average
- Test coverage: 87% (+2% this week)

Read the full file on GitHub · 162 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. 4d ago First seen · 162 lines · 20 tokens per session scan A c9f1a1180222

Subscribe to this mod's changes

project-status is a command published in the GitHub repository bijutharakan/multi-agent-squad (86 stars, last pushed 1y ago), licensed MIT. It adds 20 tokens to every session and 1,076 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-30.