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.
git clone --depth 1 https://github.com/juanmhidalgo/claude-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/commands/juanmhidalgo/claude-plugins/objection-prep)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/objection-prep"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/objection-prep/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/commands/juanmhidalgo/claude-plugins/objection-prep"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/objection-prep.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.00048 | $0.02751 |
| Opus 5.5 | $0.00019 | $0.01100 |
| Sonnet 5.5 | $0.00010 | $0.00550 |
| Haiku 4.5 | $0.00005 | $0.00275 |
Grade A, and why
objection-prep 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objection Prep
You are anticipating the questions and pushback that will come back from CSM, Sales, or the customer when the feasibility report is shared. Your goal is to give the engineer a prepped Q&A so they are not caught flat-footed.
<input_handling> The argument may be either:
- A file path — if
$ARGUMENTSlooks like a path toINTAKE-feasibility-*.mdthat exists, read it - Inline pasted feasibility report content
- A short identifier or slug — search for
INTAKE-feasibility-*<slug>*.mdin the working directory
If no feasibility report can be located, tell the user:
"This command anticipates objections to a feasibility report. Run
/intake:feasibility <request>first, then re-run this with the report path or content." </input_handling>
Phase 1: Read the Report
Extract from the feasibility report:
- The capability map (Status, Effort, Notes)
- The constraints (if any)
- The phased recommendation
- The "Excluded for this customer" list
- The Top 3 risks
Phase 2: Identify Likely Objection Categories
<objection_checklist> For each capability and risk in the report, check whether it triggers any of these objection categories. Not every category will apply — only include the ones with concrete grounding in this report.
| Category | Triggers when... | Typical asker |
|---|---|---|
| Effort objection | A capability looks cheap to the asker but is rated medium or large |
CSM, Sales, Customer |
| Hack-it-for-one-customer | A capability is large AND the customer is asking for a one-off |
Sales, occasionally CSM |
| Constraint objection | A constraint excludes a capability the customer wanted | Sales, Customer (rare from CSM) |
| Buy-vs-build | A large capability has a known SaaS substitute |
CSM, Sales |
| Existing-customer impact | A capability touches code shared with other customers | CSM (always), Engineering Manager |
| Why-not-already-built | A MISSING capability sounds obvious or table-stakes |
CSM, Customer, Sales |
| Workaround feasibility | The report lists Workarounds available today (combinations of EXISTS capabilities + manual operation), OR a MISSING capability has a manual path |
CSM, Sales |
| Pragmatic-alternative pushback | The report lists a Pragmatic alternative path (clone/extend an existing pattern instead of bespoke); the asker may push back on the trade-off |
Sales, occasionally Engineering Manager |
| Silent-bug embarrassment | A risk callout names a silent bug | CSM specifically |
| Competitor-does-this | A MISSING capability is offered by a known competitor |
Sales |
| Constraint re-litigation | The customer pushes back on their own stated constraint | Customer, Sales |
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 Changed d9799fb7793e
- 1mo ago First seen · 214 lines · 48 tokens per session scan A 59a082d94d06
objection-prep is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 2,751 once invoked, about $0.0002 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-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.