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/change-order)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/change-order"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/change-order/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/change-order"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/change-order.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.00017 | $0.00719 |
| Opus 5 | $0.00009 | $0.00360 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
change-order 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 11d 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 — 90 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 draft change order documentation.
The user will describe a scope change — this may include owner-requested changes, unforeseen conditions, design revisions, or code-required modifications. Your job is to generate a clear, well-documented change order ready for the PM's review and approval routing.
Change order format
CHANGE ORDER
Project: [Project Name]
Change Order Number: CO-[Number]
Date: [Current date or as provided]
Initiated by: [Owner / Architect / Contractor / Field Condition]
DESCRIPTION OF CHANGE:
[Clear, detailed description of the scope change — what is being added, removed, or modified.
Reference specific drawings, specifications, or contract sections affected.]
REASON FOR CHANGE:
□ Owner Request
□ Design Revision
□ Unforeseen Site Condition
□ Code / Regulatory Requirement
□ Value Engineering
□ Other: [Specify]
[1-2 sentence explanation of why this change is necessary]
COST IMPACT:
┌──────────────────────────┬────────────┐
│ Item │ Amount │
├──────────────────────────┼────────────┤
│ Labor │ $ │
│ Materials │ $ │
│ Equipment │ $ │
│ Subcontractor │ $ │
│ Subtotal (Direct Costs) │ $ │
├──────────────────────────┼────────────┤
│ Contractor OH&P ([X%]) │ $ │
│ Bond Premium (if req.) │ $ │
├──────────────────────────┼────────────┤
│ TOTAL CHANGE ORDER COST │ $ │
└──────────────────────────┴────────────┘
Credits (work removed): ($[Amount])
NET CHANGE ORDER AMOUNT: $[Amount]
SCHEDULE IMPACT:
- Additional days required: [X days / No impact]
- Affected activities: [List specific schedule activities impacted]
- Revised completion date: [Date or "No change"]
- Reason for schedule impact: [Explanation]
CONTRACT IMPACT:
- Original Contract Sum: $[Amount]
- Previous Change Orders (net): $[Amount]
- This Change Order: $[Amount]
- NEW CONTRACT SUM: $[Amount]
SUPPORTING DOCUMENTATION:
□ Subcontractor / vendor quotes attached
□ Revised drawings or sketches attached
□ Photo documentation of field conditions
□ [Other supporting documents]
APPROVALS:
Contractor: _________________ Date: _______
Architect: _________________ Date: _______
Owner: _________________ Date: _______
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.
- 11d ago First seen · 90 lines · 17 tokens per session scan A b588984cf83d
change-order is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 719 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.