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 modest-curator478/claude-skills --skill consulting-client-presentationgit clone --depth 1 https://github.com/modest-curator478/claude-skillsWrote 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/modest-curator478/claude-skills/consulting-client-presentation)<a href="https://agentmods.dev/skills/modest-curator478/claude-skills/consulting-client-presentation"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/consulting-client-presentation/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/modest-curator478/claude-skills/consulting-client-presentation"><img src="https://agentmods.dev/badge/skills/modest-curator478/claude-skills/consulting-client-presentation.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.00218 | $0.02872 |
| Opus 5 | $0.00109 | $0.01436 |
| Sonnet 5 | $0.00044 | $0.00574 |
| Haiku 4.5 | $0.00022 | $0.00287 |
Grade A, and why
consulting-client-presentation 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.
This is a copy
100% identical to consulting-client-presentation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consulting Client Presentation: Delivering Findings That Move the Engagement Forward
This skill prepares an independent consulting practitioner to present findings and recommendations to a client in a way that maintains the relationship, creates clarity about next steps, and protects the scope of the engagement.
The consulting client presentation is structurally different from an internal presentation for two reasons. First, the consultant is an outsider who has limited political capital with the people in the room. Second, the presentation is often the moment the client decides whether to extend the engagement or end it. What you say and how you say it determines both.
Most first-time consultants make the same three mistakes. They present everything they found rather than what matters most. They present recommendations without first establishing that the problem is real and agreed upon. And they close without a clear next step, which leaves the client to decide on their own timeline.
HOW TO SET UP THIS SKILL
Provide:
- What type of presentation this is: initial findings readout, mid-engagement update, final recommendations, or results review
- What you found during the engagement: the key issues, gaps, or opportunities
- What you are recommending: the specific actions you want the client to take
- Who will be in the room: just the primary contact, or additional stakeholders including leadership
- Whether there is bad news: findings that the client may not expect or may not want to hear
- Whether you want to extend the engagement and how
The Structure of a Consulting Findings Presentation
Part 1: Frame the problem before presenting findings
The most common structural mistake is opening with findings before the client has re-confirmed the problem. A week or two has passed since your initial scoping conversation. The client has been focused on other things. Starting with "here is what I found in your HubSpot" before reestablishing why they brought you in creates a context mismatch.
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 · 379 lines · 218 tokens per session scan A b2dda1403677
consulting-client-presentation is a skill published in the GitHub repository modest-curator478/claude-skills (4 stars, last pushed today), licensed MIT. It adds 218 tokens to every session and 2,872 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to consulting-client-presentation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
code-review
Pre-commit code review using code-reviewer agent for bug detection, security analysis, and quality assurance. Manual invocation only. Use before git commits to catch issues early. Blocks commits on REQUESTCHANGES verdict.
debug
Systematic debugging using error-detective and debugger agents instead of manual investigation. Triggers automatically on: error, bug, broken, failing, exception, stack trace, test failure. Orchestrates RCA-first approach with parallel agent investigation.
deep-context
Build deep codebase understanding using Capsule context, progressive-reader, and specialist agents instead of overwhelming main context. Triggers on: don't have context, understand codebase, learn about, need background. Implements progressive context building.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
workflow
Systematic task orchestration for complex multi-step tasks. Triggers automatically when detecting: complex task, multi-step work, coordinate, orchestrate, break down. Guides through Understand → Strategy → Plan → Execute → Verify phases for comprehensive systematic approach.