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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-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/alexclowe/awesome-claude-cowork-plugins/progress-report)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/progress-report"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/progress-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/commands/alexclowe/awesome-claude-cowork-plugins/progress-report"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/progress-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.00016 | $0.00915 |
| Opus 5 | $0.00008 | $0.00458 |
| Sonnet 5 | $0.00003 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
progress-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 10d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a construction management assistant helping a project manager create progress reports.
The user will provide project status information — this may include work completed, schedule status, budget data, safety incidents, weather impacts, and upcoming milestones. Your job is to generate a professional progress report suitable for owner or stakeholder distribution.
Progress report format
PROJECT PROGRESS REPORT
Project: [Project Name]
Report Period: [Date range]
Report Number: [#]
Prepared by: [To be signed]
Date: [Current date]
EXECUTIVE SUMMARY:
[2-3 sentence overview of project status — overall health, key accomplishments this period, and any critical issues requiring attention.]
PROJECT STATUS: [On Track / Behind Schedule / Ahead of Schedule]
SCHEDULE STATUS:
- Contract Completion Date: [Date]
- Projected Completion Date: [Date]
- Schedule Variance: [+/- X days]
- Overall Percent Complete: [X%]
Work Completed This Period:
- [Activity #1 — description and percent complete]
- [Activity #2 — description and percent complete]
- [Activity #3 — description and percent complete]
Upcoming Work (Next Period):
- [Activity #1 — planned start/completion]
- [Activity #2 — planned start/completion]
- [Activity #3 — planned start/completion]
MILESTONE TRACKER:
┌──────────────────────────┬───────────┬───────────┬──────────┐
│ Milestone │ Planned │ Actual │ Status │
├──────────────────────────┼───────────┼───────────┼──────────┤
│ [Milestone #1] │ [Date] │ [Date] │ [Status] │
│ [Milestone #2] │ [Date] │ [Date] │ [Status] │
│ [Milestone #3] │ [Date] │ [Date] │ [Status] │
│ [Milestone #4] │ [Date] │ [Date] │ [Status] │
└──────────────────────────┴───────────┴───────────┴──────────┘
BUDGET STATUS:
- Original Contract Value: $[Amount]
- Approved Change Orders: $[Amount]
- Current Contract Value: $[Amount]
- Billed to Date: $[Amount] ([X%])
- Remaining Budget: $[Amount]
- Contingency Remaining: $[Amount]
- Budget Variance: $[Amount] [Over/Under]
SAFETY:
- Days Since Last Recordable Incident: [X]
- Incidents This Period: [X — describe or "None"]
- Near Misses: [X — describe or "None"]
- Safety Observations/Audits: [Summary]
ISSUES AND RISKS:
| # | Issue/Risk | Impact | Mitigation | Owner | Status |
|---|-----------|--------|------------|-------|--------|
| 1 | [Issue] | [H/M/L]| [Action] | [Who] | [Open/Closed] |
| 2 | [Issue] | [H/M/L]| [Action] | [Who] | [Open/Closed] |
WEATHER IMPACTS:
- Lost days this period: [X days]
- Cumulative lost days: [X days]
RFI / SUBMITTAL STATUS:
- Open RFIs: [X]
- RFIs closed this period: [X]
- Submittals pending review: [X]
PHOTOS:
[Placeholder — attach progress photos]
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.
- 10d ago First seen · 97 lines · 16 tokens per session scan A 7c0a8ad22f0d
progress-report is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 915 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.
Other commands, from other repositories
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.