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 alexclowe/awesome-copilot-cowork-plugins --skill estimating-and-scopegit clone --depth 1 https://github.com/alexclowe/awesome-copilot-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/skills/alexclowe/awesome-copilot-cowork-plugins/estimating-and-scope)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/estimating-and-scope"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/estimating-and-scope/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/alexclowe/awesome-copilot-cowork-plugins/estimating-and-scope"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/estimating-and-scope.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.00021 | $0.00656 |
| Opus 5 | $0.00010 | $0.00328 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
estimating-and-scope 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in construction estimating and scope definition for residential and light-commercial contractors. When the user is drafting an estimate, scope of work, change order, or client update involving job costs or scope, apply this knowledge automatically.
Core competencies
Estimate structure:
- Organize work by phase: demolition, site prep, rough-in (framing, mechanical, electrical, plumbing), finish (drywall, trim, cabinets, fixtures, flooring, paint), and cleanup.
- Separate labor, materials, and subcontractors so the customer can see where the money goes.
- Every line: description, unit, quantity, unit price, line total. Totals repeat the contractor's figures — never computed by the assistant.
- Standard qualifiers: "subject to site conditions," "estimate valid for [30/60] days," a payment schedule (deposit / progress draws / final), and "DRAFT — REVIEW BEFORE SENDING" on anything not yet finalized.
Allowances and selections:
- An allowance is a placeholder dollar figure for a customer selection not yet made (tile, fixtures, appliances). Label it clearly and note that the final price adjusts to the actual selection.
- Selections drive the schedule — every selection needs a deadline, because a late selection is the most common cause of delay.
Scope definition:
- The exclusions list prevents most disputes. When in doubt, exclude it and say so explicitly.
- "Done" must be unambiguous — describe the finished condition, not just the activity.
- Distinguish contractor-provided vs. customer-provided materials.
Change-order discipline:
- A change order is the field record of added/removed work: reason, scope, cost impact, schedule impact, revised total, and a signature line.
- Customer signs before the changed work proceeds.
- The reason documents the actual discovery ("knob-and-tube exposed during demo"), not speculation about what else might exist.
Markup and margin:
- Understand the difference between markup (added to cost) and margin (percentage of price), and keep the estimate's structure consistent with whatever the contractor uses. Never change or infer a contractor's pricing.
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 · 42 lines · 21 tokens per session scan A 15dbbdc926eb
estimating-and-scope is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 656 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 skills, from other repositories
custom-daily-brief
Builds a role-tuned morning brief as a Word document covering emails that need replies, today's calendar, Teams mentions and upcoming deadlines, using section presets from an editable config file. Use when the user asks for their daily brief, morning brief, start-of-day summary or custom briefing, or wants to change…
report-attachment-analyzer
Tracks a recurring emailed report end to end. It finds new report emails in the inbox, extracts data from their attachments, appends each reporting period to a trends spreadsheet, and rewrites a summary document with period-on-period deltas and flagged anomalies. Use when the user asks to update or analyse trends for…
commitment-catcher
Scans the last 24 hours of email, Teams chats and meeting transcripts for commitments in both directions, things the user promised to others and things others promised to the user. Maintains a running commitments.md ledger with open, done and overdue statuses, flags overdue items first, and creates To Do entries with…
project-dashboard-builder
Generates a self-contained single-file HTML project dashboard (status banner, milestones, risks heat list, decisions log, links) from the tracker files in /Documents/Cowork/projects/, saved as dashboard- -YYYY-MM-DD.html. Use when the user asks for a project dashboard, a shareable or pinnable status page, an HTML…
inbox-triage
Sweeps the inbox, categorises every message as needs-reply-today, needs-reply-this-week, waiting-on-others, FYI or noise, creates reply drafts in the Drafts folder, and saves a dated triage report to OneDrive. Moves or archives mail only when a rule the user wrote in its rules file says so. Use when the user asks to…
cbo-reviewer
Reviews a proposal, business case, deck or plan in character as a Chief Business Officer archetype, covering commercial model, partnerships, deal structure, market positioning, strategic fit and opportunity cost. Produces a DRAFT review document with a verdict, findings that cite the artifact, risks and five…