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-pricing)<a href="https://agentmods.dev/commands/belkins/revenue-os/ros-pricing"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-pricing/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-pricing"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-pricing.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.00008 | $0.01469 |
| Opus 5 | $0.00004 | $0.00734 |
| Sonnet 5 | $0.00002 | $0.00294 |
| Haiku 4.5 | $0.00001 | $0.00147 |
Grade A, and why
ros-pricing 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 12d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Architecture
Arguments: $ARGUMENTS
Load Data
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" read product
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" read icp
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" read pricing
Pricing Psychology Reference
!cat "${CLAUDE_PLUGIN_ROOT}/data/pricing-psychology.json" 2>/dev/null || echo '{}'
Industry Benchmarks
!cat "${CLAUDE_PLUGIN_ROOT}/data/industry-benchmarks.json" 2>/dev/null || echo '{}'
Instructions
If $ARGUMENTS contains "analyze":
Research competitor pricing:
- WebSearch for "[competitor] pricing"
- Document tier structures
- Identify market range
- Compare to industry benchmarks
If $ARGUMENTS is empty or "design":
-
Load Context
- Read ICP data for budget expectations
- Check industry benchmarks for pricing ranges
- Review any existing pricing.json data
-
Research Competitors (WebSearch)
- Search for competitor pricing pages
- Document their tier structures and pricing
- Note feature distribution across tiers
-
Design Tier Structure
- Apply pricing psychology principles
- Create 3 tiers (anchor, target, decoy)
- Distribute features strategically
- Set prices based on ICP budget and market
-
Calculate Projections
- Revenue modeling at different customer counts
- Break-even analysis if applicable
-
Save Results
- Persist with
bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" write pricing, passing JSON on standard input
- Persist with
If $ARGUMENTS is "psychology":
Deep dive on pricing tactics:
- Explain each strategy from pricing-psychology.json
- Recommend which to apply based on product/ICP
- Show before/after examples
- Provide implementation guidance
If $ARGUMENTS is "model":
Revenue modeling mode:
- Input: Number of customers, conversion rates
- Output: MRR/ARR projections
- Break-even analysis
- Growth scenarios (conservative, moderate, aggressive)
If $ARGUMENTS is "implement":
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.
- 12d ago First seen · 206 lines · 8 tokens per session scan A 510323b401da
ros-pricing is a command published in the GitHub repository Belkins/revenue-os (29 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 1,469 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
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.
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.
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.
code-review
Multi-model code review — AI models independently review code, 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.