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-reportgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWhat 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.00018 | $0.05449 |
| Opus 5 | $0.00009 | $0.02724 |
| Sonnet 5 | $0.00004 | $0.01090 |
| Haiku 4.5 | $0.00002 | $0.00545 |
Grade A, and why
project-report 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.
How it starts
The opening of the file, as written. The whole thing — 921 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Project Report
When the user runs /project-report [project-name] [report-type], generate a comprehensive report document.
Command Syntax
/project-report # Interactive: asks for project and type
/project-report [project-name] # Interactive: asks for type
/project-report [project-name] [type] # Direct: generates specified report
Report Types:
summary- High-level project overview (default)sprint- Current/recent sprint detailed analysismilestone- Milestone progress and roadmapvelocity- Team velocity and estimation analysisfull- Complete project report (all sections)
Task 1: Identify Project and Report Type
If no parameters provided:
-
Discover projects in workspace:
find . -name "RULE.md" -type f -
Present project selection:
📊 Generate Project Report Select project: 1. {Project 1 Name} ({path}) 2. {Project 2 Name} ({path}) 3. {Project 3 Name} ({path}) Which project? (1-3) -
Present report type selection:
Select report type: 1. Summary - High-level overview (recommended for stakeholders) 2. Sprint - Current sprint detailed analysis 3. Milestone - Milestone progress and timeline 4. Velocity - Team performance metrics 5. Full - Comprehensive report (all sections) Which type? (1-5)
If parameters provided:
Parse and validate:
- Project name matches existing project
- Report type is valid (summary|sprint|milestone|velocity|full)
Task 2: Gather Report Data
Based on report type, collect relevant information:
For All Report Types:
- Project name and basic info (from RULE.md)
- Current date and report generation metadata
- Project start date and duration
For Summary Report:
- Methodology and team size
- Current sprint/phase status
- Milestone completion overview
- Key achievements (last 30 days)
- Upcoming milestones and deadlines
- High-level risks or blockers
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 · 921 lines · 18 tokens per session scan A 3715c9553e13
project-report is a command published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 5,449 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.