ros-objections

ros-objections is a command for Claude Code from Belkins/revenue-os. It costs 6 tokens per session (744 once invoked), scanned A, original, MIT.

A sales-objection assistant that uses stored product and customer-profile information to prepare replies, conversations, and practice exercises.

In plain words
What is it for?
Use it to predict likely objections, write tailored responses and example scripts, build a full sales conversation, or practise handling objections.
Why use it?
It helps you respond to customer concerns without starting from a blank page or relying on generic answers.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the revenue-os plugin — 10 commands, 1 hook shipped together

Good fit Use it to predict likely objections, write tailored responses and example scripts, build a full sales conversation, or practise handling objections.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Belkins/revenue-os
Claude Code
/plugin install revenue-os

Made for: Claude Code.

Or install revenue-os, the plugin that ships this one along with the rest of its 10 commands, 1 hook.

Wrote 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.

agentmods badge for ros-objections

README.md
[![agentmods](https://agentmods.dev/badge/commands/belkins/revenue-os/ros-objections/github.svg)](https://agentmods.dev/commands/belkins/revenue-os/ros-objections)
Your own site
<a href="https://agentmods.dev/commands/belkins/revenue-os/ros-objections"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-objections/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.

agentmods 80×15 button for ros-objections

Your own site · 80×15
<a href="https://agentmods.dev/commands/belkins/revenue-os/ros-objections"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-objections.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 744 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.00744
Opus 5 $0.00003 $0.00372
Sonnet 5 $0.00001 $0.00149
Haiku 4.5 $0.00001 $0.00074

Measured 10d ago against content hash a74d5ff2ed18, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

ros-objections 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 10d 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.

plugin/commands/ros-objections.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Objection Handler

Arguments: $ARGUMENTS

Load Data

!bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" read product !bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" read icp !cat "${CLAUDE_PLUGIN_ROOT}/data/objection-library.json" 2>/dev/null

Instructions

If $ARGUMENTS is empty or "generate":

Generate likely objections for this specific product:

  1. Based on ICP (budget concerns, decision process)
  2. Based on product type (build vs buy, switching cost)
  3. Based on pricing (if known)

Provide responses customized to this product.

If $ARGUMENTS contains "handle":

Provide detailed response to the specific objection:

  • Multiple response tactics
  • Customized for this product
  • Example scripts

If $ARGUMENTS is "script":

Generate a full sales conversation script including:

  • Opening
  • Discovery questions
  • Product presentation
  • Objection handling
  • Closing

If $ARGUMENTS is "practice":

Interactive objection practice mode.

Output Format

## Objection Handling: [Product Name]

### Most Likely Objections for Your ICP

Based on [ICP name] selling [Product]:

1. **[Objection 1]**
   - Why they say it: [psychology]
   - Response: [customized response]

2. **[Objection 2]**
   - Why they say it: [psychology]
   - Response: [customized response]

3. **[Objection 3]**
   - Why they say it: [psychology]
   - Response: [customized response]

### Universal Responses (Memorize These)

**Price Objection Framework**
1. Acknowledge: "I understand price is a concern..."
2. Question: "What would [outcome] be worth to you?"
3. Reframe: "Compared to [alternative], this is..."
4. Proof: "Our customers typically see ROI in..."

**Competitor Objection Framework**
1. Acknowledge: "That's a great product..."
2. Question: "What do you wish it did better?"
3. Differentiate: "The key difference is..."
4. Offer: "Would you like to see a comparison?"

**Timing Objection Framework**
1. Acknowledge: "I understand timing is tricky..."
2. Question: "When would be better?"
3. Urgency: "The cost of waiting is..."
4. Easy start: "We could start with just..."

### Quick Reference Card

| Objection | Quick Response |
|-----------|----------------|
| Too expensive | "What would [outcome] be worth to you?" |
| No budget | "When's your next budget cycle?" |
| Using competitor | "What do you wish it did better?" |
| Build ourselves | "How many engineer-months would that take?" |
| Need approval | "What info would help you make the case?" |
| Prove ROI | "Let's run a measured pilot." |
| Tried before | "What didn't work? We might be different." |

### Role-Play Scenarios

**Scenario 1: Price Pushback**
[Example dialogue]

**Scenario 2: Competitor Lock-in**
[Example dialogue]

**Scenario 3: Need to Think**
[Example dialogue]

Read the full file on GitHub · 112 lines

Changes

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.

  1. 10d ago First seen · 112 lines · 6 tokens per session scan A a74d5ff2ed18

Subscribe to this mod's changes

ros-objections is a command published in the GitHub repository Belkins/revenue-os (29 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 744 once invoked, about $0.0000 per session on Opus 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-08-30.