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/legacybridge-tech/claude-plugins/project-statusgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWrote 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/legacybridge-tech/claude-plugins/project-status)<a href="https://agentmods.dev/commands/legacybridge-tech/claude-plugins/project-status"><img src="https://agentmods.dev/badge/commands/legacybridge-tech/claude-plugins/project-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.00021 | $0.02777 |
| Opus 5 | $0.00010 | $0.01388 |
| Sonnet 5 | $0.00004 | $0.00555 |
| Haiku 4.5 | $0.00002 | $0.00278 |
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 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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Overview
When the user runs /project-status, provide a comprehensive overview of all project activities, progress, and health.
Task 1: Discover Projects
Scan the workspace to find all ProjectMaster-managed projects:
-
Find all RULE.md files:
find . -name "RULE.md" -type f -
For each RULE.md found:
- Read the file
- Check if it has ProjectMaster configuration (methodology field)
- Extract project name (from RULE.md or parent directory name)
- Note project location
-
Identify primary project:
- If in a project directory: That project
- If in workspace root with multiple projects: All projects
- If single project in workspace: That project
Task 2: Gather Project Data
For each project, collect comprehensive status information:
2.1 Basic Project Info
From RULE.md:
- Project name
- Methodology (Scrum, Kanban, Waterfall, etc.)
- Team size
- Start date
2.2 Current Sprint/Iteration Status
Read active sprint document:
grep -r "status: active" sprints/*/sprint-plan.md
Extract:
- Sprint number and goal
- Start and end dates
- Days remaining
- Story completion (X/Y stories, A/B points)
- Velocity percentage
- Blockers (if any)
- Team members and assignments
2.3 Milestone Status
Read milestones.yaml:
- Total milestones
- Completed milestones
- In-progress milestones
- Next milestone due
- Any delayed milestones
- Overall completion percentage
2.4 Recent Activity
Check Recent Activity section in project README.md:
- Last 5-7 activities
- Types: meetings, sprint updates, milestone completions, document additions
2.5 Team Activity
Scan recent content for @mentions:
- Who's been active recently
- Current assignments
- Upcoming responsibilities
2.6 Governance Health
Quick governance check:
- RULE.md present and valid
- README.md files up to date
- Directory structure intact
- milestones.yaml valid
2.7 Upcoming Items
- Next sprint start (if Scrum)
- Upcoming milestones
- Scheduled meetings
- Deadlines approaching
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 · 484 lines · 21 tokens per session scan A f208528412e3
project-status is a command published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 2,777 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.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.