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 matellez/claude-skills --skill consulting-engagement-setupgit clone --depth 1 https://github.com/matellez/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/matellez/claude-skills/consulting-engagement-setup)<a href="https://agentmods.dev/skills/matellez/claude-skills/consulting-engagement-setup"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/consulting-engagement-setup/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/matellez/claude-skills/consulting-engagement-setup"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/consulting-engagement-setup.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.00223 | $0.02966 |
| Opus 5.5 | $0.00089 | $0.01186 |
| Sonnet 5.5 | $0.00045 | $0.00593 |
| Haiku 4.5 | $0.00022 | $0.00297 |
Grade A, and why
consulting-engagement-setup 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 2mo 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-engagement-setup — 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consulting Engagement Setup: Scoping, Pricing, and Protecting the Work
This skill sets up an independent consulting engagement correctly from the start. Most first-time consultants either underprice the work, underscope the deliverables, or both. The result is an engagement that expands without additional compensation, produces resentment, and ends the client relationship faster than the work would have ended it naturally.
The goal of this skill is not to protect the consultant from the client. It is to create a clear shared understanding of what is being purchased so that both sides can evaluate whether the work was done correctly. Ambiguity in scope is not a negotiating advantage. It is a liability that collects interest until it is paid with a damaged relationship.
HOW TO SET UP THIS SKILL
Provide:
- What the client has asked for, in their words if possible
- How the conversation started (referral, inbound, prior relationship)
- Whether a rate has been discussed or if that conversation is still ahead
- Your current read on what the client actually needs versus what they asked for
- Any constraints: timeline, budget signals, internal politics at the client
- Whether this is your first consulting engagement or you have done this before
The Conversation Before the Proposal
The most important conversation in a consulting engagement happens before any proposal is written. Most first-time consultants skip it because they are eager to win the work. Skipping it is the reason most engagements go wrong.
The pre-proposal conversation has one goal: understand the problem the client is actually trying to solve, not the solution they have already decided they want.
A client who says "we need someone to clean up our HubSpot" may actually need attribution rebuilt because the CEO is asking why marketing cannot show pipeline contribution. Cleaning up HubSpot is one step in that solution, not the solution itself. A consultant who scopes to the stated request will finish the cleanup and leave the client unsatisfied because the underlying problem is unchanged.
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.
- 2mo ago First seen · 390 lines · 223 tokens per session scan A 200b95276bdd
consulting-engagement-setup is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 223 tokens to every session and 2,966 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to consulting-engagement-setup, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally and checks a move from existing RudderStack events: validates captures against the v0.3 schema, joins, switches and legacy events. Use when testing AI events, comparing old and new tracking, or when AI or MCP events look wrong or missing.
helius
Skill "helius" from helius-labs/core-ai, covering helius — build on solana, prerequisites, 1. helius mcp server, 2. mcp router surface and 3. api key.