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 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/client-management)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/client-management"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/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/client-management"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/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.00016 | $0.00615 |
| Opus 5.5 | $0.00006 | $0.00246 |
| Sonnet 5.5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
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 23d 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:
- client-management — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to manage client relationships effectively in event planning. When the user is preparing client-facing materials, proposals, or communications, apply these principles automatically.
Proposal writing
Structure and presentation:
- Lead with the event vision — clients buy the experience, not the line items
- Present scope of services clearly with inclusions and exclusions
- Budget breakdowns should be organized by category with ranges where costs are variable
- Include planning timeline with client decision points
- Terms and conditions should be clear but not overwhelming
- Professional formatting that reflects the planner's brand
Pricing strategies:
- Present planning fee separate from vendor costs for transparency
- Offer tiered service levels when appropriate (full planning, partial, day-of)
- Include contingency line item as standard (educate clients on why)
- Be transparent about how vendor commissions or referral fees work, if applicable
Expectation management
Setting expectations early:
- Define communication cadence (weekly emails, monthly meetings, etc.)
- Establish decision timelines and their impact on availability and pricing
- Clarify what requires additional budget vs what is included
- Set realistic expectations for vendor response times and booking timelines
- Document everything in writing — verbal agreements lead to misunderstandings
Managing scope creep:
- When clients request additions, frame as change orders with cost impact
- Present options: add to scope with additional cost, substitute for existing item, or defer
- Keep a running change log to review at milestones
- Reframe "just one more thing" as a positive: "Great idea — here's how we can incorporate it"
Change communication
Delivering changes:
- Lead with context and rationale before the change itself
- Present the impact (budget, timeline, guest experience)
- Offer alternatives or solutions alongside the problem
- Get written approval for any changes affecting budget or scope
- Follow up change conversations with a written summary
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.
- 23d ago First seen · 70 lines · 16 tokens per session scan A 4b0fe68c5074
client-management is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 615 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-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-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-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.