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 skills add w95/awesome-claude-corporate-skills --skill project-status-reportgit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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/skills/w95/awesome-claude-corporate-skills/project-status-report)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/project-status-report"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/project-status-report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/project-status-report"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/project-status-report.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.01839 |
| Opus 5 | $0.00013 | $0.00920 |
| Sonnet 5 | $0.00005 | $0.00368 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
project-status-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 9d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Report Builder
Overview
Create comprehensive project status reports that provide executives and stakeholders with accurate visibility into project health, progress, and risks. These reports combine RAG status indicators, milestone tracking, and actionable insights to enable informed decision-making.
Key Report Sections
1. Executive Summary (1 page)
Concise overview for time-constrained stakeholders:
- Overall Status: RED / AMBER / GREEN with 2-3 sentence explanation
- Key Wins This Period: Top 2-3 accomplishments
- Critical Issues: Top 1-2 blockers requiring escalation
- Next Period Focus: What's next and key milestones
- Budget Status: On track / at risk with % utilization
2. RAG Status Framework
RED (Critical):
- Major milestones missed or at severe risk
- Budget overrun >15%
- Resource gaps impacting delivery
- Technical blockers with no clear solution
- Dependencies unresolved
AMBER (At Risk):
- Milestones at risk of missing (within 5 days)
- Budget at 80%+ utilization
- Moderate resource constraints
- Known risks with mitigation in progress
- Some dependency delays
GREEN (On Track):
- Milestones on schedule
- Budget under 80% utilization
- Resources allocated and productive
- Risks identified with controls
- Dependencies resolved or on track
3. Milestone Tracking
Milestone | Target Date | Status | % Complete | Owner | Notes
-----------|-------------|--------|-----------|-------|-------
Phase 1 | Jan 31 | GREEN | 100% | John | Delivered on time
Phase 2 | Feb 28 | AMBER | 45% | Sarah | 5-day slip risk
Phase 3 | Mar 31 | GREEN | 15% | Mike | On schedule
4. Resource Utilization
Resource | Allocated | Utilized | Capacity | Status | Notes
---------|-----------|----------|----------|--------|------
Dev Team | 8 FTE | 7.2 FTE | 90% | GREEN | 1 developer on vacation
QA | 2 FTE | 1.5 FTE | 75% | GREEN | Peak testing phase coming
PM | 1 FTE | 1 FTE | 100% | AMBER | Overallocated across projects
Design | 1 FTE | 0.3 FTE | 30% | RED | Backlog review needed
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.
- 9d ago First seen · 208 lines · 25 tokens per session scan A 8c56e594db3c
project-status-report is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 1,839 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-09-03.
Other skills, from other repositories
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.