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-audit)<a href="https://agentmods.dev/commands/belkins/revenue-os/ros-audit"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-audit/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-audit"><img src="https://agentmods.dev/badge/commands/belkins/revenue-os/ros-audit.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.00010 | $0.01574 |
| Opus 5 | $0.00005 | $0.00787 |
| Sonnet 5 | $0.00002 | $0.00315 |
| Haiku 4.5 | $0.00001 | $0.00157 |
Grade A, and why
ros-audit 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revenue Readiness Audit
Arguments: $ARGUMENTS
Load All 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 value-prop
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" read pricing
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" list-outreach
Industry Benchmarks Reference
!cat "${CLAUDE_PLUGIN_ROOT}/data/industry-benchmarks.json" 2>/dev/null || echo '{}'
Instructions
If $ARGUMENTS is empty or "full":
Perform comprehensive audit:
-
Score Each Area (0-100 total)
Area Max Points Scoring Criteria Product Analysis 15 Has name: 10pts, has features: +5pts ICP Definition 25 Has primary: 15pts, has where_to_find: +5pts, validated: +5pts Value Proposition 25 Has headline: 15pts, has benefits: +5pts, has angles: +5pts Pricing 15 Has tiers: 10pts, has psychology: +5pts Sales Collateral 10 Has outreach sequences: 10pts Distribution 10 Has channels defined: 10pts -
Identify Critical Gaps
- Any area scoring 0 is CRITICAL
- Any area scoring < 50% of max is WARNING
- Recommend a specific
/revenue-os:ros-*command for each gap
-
Create Action Plan
- 2-week sprint with prioritized daily actions
- Focus on highest-impact gaps first
- Reference industry benchmarks for context
-
Project Revenue Timeline
- Use industry benchmarks to estimate:
- Time to first sale
- Time to first $1k MRR
- Time to first $10k MRR
- Use industry benchmarks to estimate:
If $ARGUMENTS is "quick":
Show just the score breakdown without detailed recommendations.
If $ARGUMENTS is "export":
Run bash "${CLAUDE_PLUGIN_ROOT}/scripts/utils/storage.sh" export and return the
reported path. Do not read or write managed export paths directly.
Output Format
## Revenue Readiness Audit: [Product Name]
**Audit Date**: [Date]
**Codebase**: [Path if available]
---
### Overall Score: XX/100
[████████░░░░░░░░░░░░] XX%
**Status**: [Just Starting | Building Foundation | Making Progress | Almost Ready | Launch Ready]
---
### Detailed Breakdown
| Area | Score | Status | Action Required |
|------|-------|--------|-----------------|
| Product Analysis | X/15 | ✓/⚠/✗ | [Action or "Complete"] |
| ICP Definition | X/25 | ✓/⚠/✗ | [Action or "Complete"] |
| Value Proposition | X/25 | ✓/⚠/✗ | [Action or "Complete"] |
| Pricing | X/15 | ✓/⚠/✗ | [Action or "Complete"] |
| Sales Collateral | X/10 | ✓/⚠/✗ | [Action or "Complete"] |
| Distribution | X/10 | ✓/⚠/✗ | [Action or "Complete"] |
**Legend**: ✓ Complete | ⚠ Partial | ✗ Missing
---
### Critical Gaps (Fix These First)
1. ❌ **[Most Critical Gap]**
- Impact: [Why this matters]
- Fix: Run `/revenue-os:ros-<command>`
- Time: ~[X minutes]
2. ❌ **[Second Gap]**
- Impact: [Why this matters]
- Fix: Run `/revenue-os:ros-<command>`
- Time: ~[X minutes]
---
### What's Working
1. ✓ **[Strength 1]** - [Brief explanation]
2. ✓ **[Strength 2]** - [Brief explanation]
---
### Your 2-Week Sprint to Revenue
**Week 1: Foundation (Days 1-5)**
| Day | Task | Command | Est. Time |
|-----|------|---------|-----------|
| 1 | Define ideal customer | `/revenue-os:ros-icp` | 30 min |
| 2 | Polish value proposition | `/revenue-os:ros-value-prop` | 30 min |
| 3 | Research competitors | `/revenue-os:ros-competitors` | 45 min |
| 4 | Design pricing | `/revenue-os:ros-pricing` | 30 min |
| 5 | Handle objections prep | `/revenue-os:ros-objections` | 20 min |
**Week 2: Distribution (Days 6-14)**
| Day | Task | Command | Est. Time |
|-----|------|---------|-----------|
| 6-7 | Create landing page | `/revenue-os:ros-landing-page` | 1 hr |
| 8-9 | Generate outreach | `/revenue-os:ros-outreach` | 45 min |
| 10-14 | Execute outreach | Manual | Ongoing |
---
### Revenue Projection
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 · 193 lines · 10 tokens per session scan A 3b0a04f17efe
ros-audit is a command published in the GitHub repository Belkins/revenue-os (29 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 1,574 once invoked, about $0.0001 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.