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-competitors)<a href="https://agentmods.dev/commands/belkins/revenue-os/ros-competitors"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-competitors/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-competitors"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-competitors.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.00005 | $0.00577 |
| Opus 5 | $0.00003 | $0.00289 |
| Sonnet 5 | $0.00001 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
ros-competitors 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence
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/competitor-analysis.json" 2>/dev/null
Instructions
If $ARGUMENTS contains "analyze":
Deep dive on the named competitor:
- WebSearch for their website, pricing page, features
- WebSearch for reviews (G2, Capterra, Reddit mentions)
- Analyze positioning, pricing, strengths, weaknesses
- Identify attack angles
If $ARGUMENTS is empty or "matrix":
- Identify competitors (from product analysis or ask user)
- WebSearch for each competitor
- Create comparison matrix
- Identify your unique advantages
If $ARGUMENTS is "gaps":
Focus on finding market gaps:
- WebSearch for "[category] missing features"
- Search for competitor complaints
- Identify underserved segments
If $ARGUMENTS is "steal":
Generate competitor migration campaign:
- Identify competitor weaknesses
- Create targeted outreach for their users
- Generate comparison content
Output Format
## Competitive Intelligence: [Your Product]
### Competitors Analyzed
- [Competitor 1] - [brief description]
- [Competitor 2] - [brief description]
### Feature Comparison Matrix
| Feature | You | Comp 1 | Comp 2 |
|---------|-----|--------|--------|
| [Feature] | ✓/✗ | ✓/✗ | ✓/✗ |
### Pricing Comparison
| | You | Comp 1 | Comp 2 |
|-|-----|--------|--------|
| Entry Price | $X | $X | $X |
| Pro Price | $X | $X | $X |
### Vulnerability Analysis
**[Competitor 1]**
- Weakness: [specific issue from research]
- Attack angle: "[Your product] does X that they can't"
- Evidence: "[quote from review/complaint]"
### Your Unique Advantages
1. [Advantage 1]
2. [Advantage 2]
3. [Advantage 3]
### Competitor Migration Campaign
**Target**: [Competitor] users unhappy with [issue]
**Outreach**:
Subject: Switching from [Competitor]?
[Email template targeting their users]
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 · 91 lines · 5 tokens per session scan A b3bb9a130738
ros-competitors is a command published in the GitHub repository Belkins/revenue-os (29 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 577 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.