Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git 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/plugins/belkins/revenue-os/plugin)<a href="https://agentmods.dev/plugins/belkins/revenue-os/plugin"><img src="https://agentmods.dev/badge/plugins/belkins/revenue-os/plugin/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/plugins/belkins/revenue-os/plugin"><img src="https://agentmods.dev/badge/plugins/belkins/revenue-os/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
revenue-os 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 1mo 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "revenue-os",
"displayName": "Revenue OS",
"version": "1.0.6",
"description": "A practical monetization toolkit for moving from code to customers to revenue.",
"author": {
"name": "Vladyslav Podoliako",
"url": "https://vladyslavpodoliako.com/"
},
"repository": "https://github.com/Belkins/revenue-os",
"homepage": "https://github.com/Belkins/revenue-os#readme",
"license": "MIT",
"keywords": [
"monetization",
"sales",
"marketing",
"revenue",
"ideal-customer-profile",
"value-proposition",
"pricing",
"outreach",
"customer-acquisition"
],
"commands": [
"./commands/ros.md",
"./commands/ros-audit.md",
"./commands/ros-competitors.md",
"./commands/ros-first-dollar.md",
"./commands/ros-icp.md",
"./commands/ros-landing-page.md",
"./commands/ros-objections.md",
"./commands/ros-outreach.md",
"./commands/ros-pricing.md",
"./commands/ros-value-prop.md"
]
}
What it installs
The manifest is a name and a version. 10 commands, 1 hook travel with it, and installing the plugin installs all of them — 91 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command ros-audit A 10 tokens
- Command ros-pricing A 8 tokens
- Command ros A 8 tokens
- Command ros-first-dollar A 11 tokens
- Command ros-icp A 14 tokens
- Command ros-value-prop A 13 tokens
- Command ros-landing-page A 9 tokens
- Command ros-objections A 6 tokens
- Command ros-outreach A 7 tokens
- Command ros-competitors A 5 tokens
- Hook SessionStart A not measured
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.
- 1mo ago First seen · 38 lines scan A 77550da16065
revenue-os is a plugin published in the GitHub repository Belkins/revenue-os (28 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
alibabacloud-opc
Alibaba Cloud OPC (one-person company) package selection and provisioning for solo developers, with an itemized monthly cost confirmation before any charge.
dokumenty
Operacje na dokumentach: konwersja PDF/Office do Markdown (markitdown, opendataloader-pdf), redlining .docx z Track Changes (redline-docx-pl), anonimizacja i pseudonimizacja PII (let-it-be), terminy procesowe (terminy-procesowe-pl), klauzule umowne (klauzule-kontraktowe-pl), kalkulatory procesowe…
dev-mcp
Narzedzia deweloperskie MateMatic (advanced): spec-driven development, kanon budowy MCP serverow, recenzent PR dla LegalTech AI, generator instalatora marketplace. Bez konektorow.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
craft
Full-stack developer toolkit with integrated workflow automation - 48 commands, 2 agents, 41 skills with standardized dry-run preview mode (29 with --dry-run support). Code, git, site, docs, testing, architecture, CI, distribution, teaching workflows, planning, release pipeline, and ADHD-friendly features including…
talk-to-anyone
Turn any public figure into your personal coach, living or historical. /coach researches the person across the web, pulls real transcripts when they have video anywhere on YouTube, builds a persona, and talks to you as them until you switch or end.