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 design-client-managementgit 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/design-client-management)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/design-client-management"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/design-client-management/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/design-client-management"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/design-client-management.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.00018 | $0.00762 |
| Opus 5.5 | $0.00007 | $0.00305 |
| Sonnet 5.5 | $0.00004 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
design-client-management 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 13d 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:
- design-client-management — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to manage client relationships in interior design practice. When the user is preparing proposals, client communications, or project management documents, apply these principles automatically.
Proposal writing
Structure design proposals to build trust and set clear expectations:
Key elements of effective proposals:
- Lead with the client's vision, not the designer's credentials
- Translate design ideas into lifestyle or business outcomes the client cares about
- Be specific about scope — vague proposals lead to scope creep
- Present fees confidently with clear value context
- Include a detailed exclusions section to prevent misunderstandings
Fee structure guidance:
- Flat fee: Best for well-defined scopes; clients appreciate cost certainty
- Hourly: Best for advisory roles or projects with uncertain scope
- Cost-plus: Common for procurement-heavy projects; explain the markup transparently
- Hybrid: Flat design fee + procurement markup balances predictability with flexibility
- Always tie payment milestones to project milestones, not calendar dates
Scope management
Proactively manage project scope to protect the designer's time and the client relationship:
- Document the agreed scope clearly at project start
- When clients request additions, frame them as change orders — not complaints, but professional process
- Provide cost and timeline impact for every scope change before proceeding
- Keep a running log of scope changes for reference
- Distinguish between "included revisions" and "additional scope" in the original agreement
Change order communication
Communicate changes with transparency and professionalism:
- Client-requested changes: Acknowledge the request positively, then present the impact clearly
- Field conditions: Explain what was discovered, why it wasn't foreseeable, and present options
- Designer recommendations: Frame as opportunities to improve the project, with clear cost-benefit context
- Always present at least two options when possible — clients appreciate having choices
- Get written approval before proceeding with any change that affects budget or timeline
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.
- 13d ago First seen · 81 lines · 18 tokens per session scan A 2881488e4368
design-client-management is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (29 stars, last pushed 12d ago), licensed MIT. It adds 18 tokens to every session and 762 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-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-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-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.