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.
/plugin marketplace add Belkins/revenue-os/plugin install revenue-osWrote 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/belkins/revenue-os/ros-objections)<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.
<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>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.00006 | $0.00744 |
| Opus 5 | $0.00003 | $0.00372 |
| Sonnet 5 | $0.00001 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00074 |
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.
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:
- Based on ICP (budget concerns, decision process)
- Based on product type (build vs buy, switching cost)
- 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]
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.
- 10d ago First seen · 112 lines · 6 tokens per session scan A a74d5ff2ed18
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.
Other commands, from other repositories
save
Save current work state for next session. Creates/updates .planning/ files (CHECKPOINT.md, STATE.md, settings.json) so Heimdall resumes with full context. NOT a rewind — saves forward progress. Run before closing a session or at any milestone.
maintain
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.
code-review
Multi-model code review — AI models independently review code, then converge on findings.
plan-review
Multi-model plan review — AI models independently plan, then converge on the best approach.
review
Multi-model review — AI models independently review any document or general topic, then converge on findings.
autonomy
Set Heimdall autonomy (1=Guided, 2=Checkpoint, 3=Full Auto) — how much the agent does before asking. Use with a number, +/- to cycle, or no argument to show current.