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-claude-cowork-plugins --skill estimating-and-scopegit 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/skills/alexclowe/awesome-claude-cowork-plugins/estimating-and-scope)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/estimating-and-scope"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-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-claude-cowork-plugins/estimating-and-scope"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-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.5 | $0.00008 | $0.00262 |
| Sonnet 5.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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- estimating-and-scope — 100% identical, 0 lines differ
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.
- 1mo 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-claude-cowork-plugins (31 stars, last pushed 13d ago), licensed MIT. It adds 21 tokens to every session and 656 once invoked, about $0.0001 per session on Opus 5.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-24.
Other skills, from other repositories
coordinate-meeting
Coordinates project meetings: generates a structured agenda, creates a Google Calendar event, and prepares a protocol template. Covers 5 meeting types across the full project lifecycle — tasks #6, #15, #17, #20, #26. Meeting types: Go/No-Go (Phase 1, #6), Client Demo (Phase 3, #15), Sprint Planning (Phase 4, #17)…
generate-budget
Generates a detailed project budget (project-budget.xlsx) for Phase 2 — Planning, based on preliminary-estimate.xlsx and resource-plan.md. Produces a single baseline scenario structured by project phases and cost categories (team, infrastructure, GTM), with a contingency reserve as a separate line item. Covers task #9…
generate-change-impact
Generates a change impact assessment file (change-impact-CR-001.xlsx) for Phase 4 — Development. PM describes a scope change request; the agent classifies the change (scope / budget / timeline / resource), analyzes impact on project-plan.md and project-budget.xlsx, calculates timeline delta, budget delta, and risk…
generate-estimate
Generates a preliminary timeline and budget estimate for an IT project (Phase 1 — Initiation). Reads available project files (client questionnaire, project charter, constraints, team list), applies analogy-based estimation using built-in agent knowledge of typical IT projects, and produces a three-scenario (optimistic…
generate-approval-letter
Generates an approval-letter.md email body and an email-tpl-approval.md template for Phase 2 — Planning. Reads project-plan.md, project-budget.xlsx, and resource-plan.md to compose a formal approval request addressed to all Approver-level stakeholders from stakeholder-map.md. Produces two artifacts: the letter email…
generate-questionnaire
A questionnaire builder for IT projects. It creates either a client questionnaire for gathering requirements at the start or a lessons-learned questionnaire for the team at the end, and can organize the answers.