Borrowing it
Nothing to install: this file belongs to Belkins/revenue-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Belkins/revenue-os/main/CLAUDE.mdgit clone --depth 1 https://github.com/Belkins/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/instructions/belkins/revenue-os/claude-md)<a href="https://agentmods.dev/instructions/belkins/revenue-os/claude-md"><img src="https://agentmods.dev/badge/instructions/belkins/revenue-os/claude-md/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/instructions/belkins/revenue-os/claude-md"><img src="https://agentmods.dev/badge/instructions/belkins/revenue-os/claude-md.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.01851 | $0.01851 |
| Opus 5 | $0.00925 | $0.00925 |
| Sonnet 5 | $0.00370 | $0.00370 |
| Haiku 4.5 | $0.00185 | $0.00185 |
Grade A, and why
revenue-os CLAUDE.md 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revenue OS - Development Context
Project Overview
Revenue OS is a Claude Code plugin that helps developers monetize their products. It provides a systematic approach to go from code to customers to cash.
Tagline: "From code to customers to cash"
Architecture
revenue-os/
├── .claude-plugin/
│ └── marketplace.json # Belkins catalog; source is exactly ./plugin
├── plugin/ # Exact package installed in the user's plugin cache
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest with command definitions
│ ├── commands/ # Namespaced Revenue OS slash commands
│ ├── data/ # Bundled templates and frameworks
│ ├── hooks/
│ │ └── hooks.json # Session lifecycle hooks
│ ├── scripts/
│ │ ├── core/
│ │ │ └── init-session.sh
│ │ └── utils/
│ │ ├── safe_store.py # No-follow, atomic storage boundary
│ │ └── storage.sh # Command-facing storage CLI
│ └── LICENSE
├── scripts/
│ └── validate-repository.sh # Preflight + official validator + install smoke
├── tests/
│ ├── data-migration-test.sh # Managed-data migration tests
│ └── validator-test.sh # Validator mutation fixtures
├── CLAUDE.md # This file
└── README.md # User documentation
Data Flow
Commands build on each other in this recommended order:
/revenue-os:ros-icpanalyzes codebase → saves to${CLAUDE_PLUGIN_DATA}/icp.json/revenue-os:ros-value-propuses ICP data → saves to${CLAUDE_PLUGIN_DATA}/value-prop.json/revenue-os:ros-pricinguses ICP + competitor research → saves to${CLAUDE_PLUGIN_DATA}/pricing.json/revenue-os:ros-outreachuses ICP + value prop → generates sequences in${CLAUDE_PLUGIN_DATA}/outreach//revenue-os:ros-auditreads all data → provides comprehensive score
Data Storage
All persistent data is stored in the ${CLAUDE_PLUGIN_DATA}/ directory supplied
by Claude Code. plugin/scripts/core/init-session.sh performs a copy-only, one-time
migration from legacy ~/.claude/revenue-os/ storage. It never overwrites
canonical files or deletes the legacy source; conflicts leave the migration
unmarked so a later session can retry.
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 · 199 lines · 1,851 tokens per session scan A 6fb55a802315
revenue-os CLAUDE.md is an instructions file published in the GitHub repository Belkins/revenue-os (29 stars, last pushed 1mo ago), licensed MIT. It adds 1,851 tokens to every session, about $0.0093 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.